[
https://issues.apache.org/jira/browse/PHOENIX-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485592#comment-14485592
]
Rajeshbabu Chintaguntla commented on PHOENIX-1126:
--------------------------------------------------
Better to have one change but without that some corner cases write will be
retried. The change is like in batchMutate we check for memory and if we reach
flush threshold RegionTooBusyException will be thrown and write will be
retried. We should have batchMutate without resource check for this.
> Make local index updates transactional with the data updates
> ------------------------------------------------------------
>
> Key: PHOENIX-1126
> URL: https://issues.apache.org/jira/browse/PHOENIX-1126
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: rajeshbabu
>
> Given that local index updates happen on the same region server as the data
> updates, we should be able to make them transaction: either both the data and
> index updates succeed, or neither of them do. I seem to remember [~lhofhansl]
> mentioned that the all or none behavior of HRegion.mutateRowsWithLocks()
> could be emulated across tables if you knew that the mutations were all local.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
