[
https://issues.apache.org/jira/browse/PHOENIX-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3793:
----------------------------------
Description:
On the client-side, Phoenix sends batched mutations in row key order. We should
do the same on the server-side when we issue batched mutations to avoid
deadlocks (see HBASE-17924). There are two places in which we submit batched
mutations on the server-side:
- In UngroupedAggregateRegionObserver.commit()
- In ParallelWriterIndexCommitter.write()
was:On the client-side, Phoenix sends batched mutations in row key order. We
should do the same on the server-side when we issue batched mutations to avoid
deadlocks (see HBASE-17924).
> Sort batch mutations on server-side to prevent deadlocks
> --------------------------------------------------------
>
> Key: PHOENIX-3793
> URL: https://issues.apache.org/jira/browse/PHOENIX-3793
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
>
> On the client-side, Phoenix sends batched mutations in row key order. We
> should do the same on the server-side when we issue batched mutations to
> avoid deadlocks (see HBASE-17924). There are two places in which we submit
> batched mutations on the server-side:
> - In UngroupedAggregateRegionObserver.commit()
> - In ParallelWriterIndexCommitter.write()
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
