[jira] [Updated] (HBASE-13896) Multi-actions in hbase-client could fall in dead loop when region moves.
[ https://issues.apache.org/jira/browse/HBASE-13896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-13896: --- Fix Version/s: (was: 0.98.15) 0.98.16 > Multi-actions in hbase-client could fall in dead loop when region moves. > > > Key: HBASE-13896 > URL: https://issues.apache.org/jira/browse/HBASE-13896 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.13 >Reporter: Victor Xu >Assignee: Victor Xu >Priority: Minor > Fix For: 0.98.16 > > Attachments: HBASE-13896-0.98-v1.patch > > > The code in AsyncProcess.receiveGlobalFailure() use only one row to update > region cache in hbase-client. When we use HTable.put(List) api to write > some data which are from different regions and some of them are > moved/balanced while writing, the client may fall into a dead loop: > multi-actions fails because some regions moved => update only one region > cache(not the wrong ones) => resubmit => failed again. > It only happens in 0.98 branch, and the master branch is ok. > The patch followed should update all cached region locations when > multi-actions fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13896) Multi-actions in hbase-client could fall in dead loop when region moves.
[ https://issues.apache.org/jira/browse/HBASE-13896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-13896: --- Fix Version/s: (was: 0.98.14) 0.98.15 > Multi-actions in hbase-client could fall in dead loop when region moves. > > > Key: HBASE-13896 > URL: https://issues.apache.org/jira/browse/HBASE-13896 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.13 >Reporter: Victor Xu >Assignee: Victor Xu >Priority: Minor > Fix For: 0.98.15 > > Attachments: HBASE-13896-0.98-v1.patch > > > The code in AsyncProcess.receiveGlobalFailure() use only one row to update > region cache in hbase-client. When we use HTable.put(List) api to write > some data which are from different regions and some of them are > moved/balanced while writing, the client may fall into a dead loop: > multi-actions fails because some regions moved => update only one region > cache(not the wrong ones) => resubmit => failed again. > It only happens in 0.98 branch, and the master branch is ok. > The patch followed should update all cached region locations when > multi-actions fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13896) Multi-actions in hbase-client could fall in dead loop when region moves.
[ https://issues.apache.org/jira/browse/HBASE-13896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor Xu updated HBASE-13896: -- Attachment: HBASE-13896-0.98-v1.patch Submit a small patch to fix it. > Multi-actions in hbase-client could fall in dead loop when region moves. > > > Key: HBASE-13896 > URL: https://issues.apache.org/jira/browse/HBASE-13896 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.13 >Reporter: Victor Xu >Priority: Minor > Attachments: HBASE-13896-0.98-v1.patch > > > The code in AsyncProcess.receiveGlobalFailure() use only one row to update > region cache in hbase-client. When we use HTable.put(List) api to write > some data which are from different regions and some of them are > moved/balanced while writing, the client may fall into a dead loop: > multi-actions fails because some regions moved => update only one region > cache(not the wrong ones) => resubmit => failed again. > It only happens in 0.98 branch, and the master branch is ok. > The patch followed should update all cached region locations when > multi-actions fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13896) Multi-actions in hbase-client could fall in dead loop when region moves.
[ https://issues.apache.org/jira/browse/HBASE-13896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-13896: -- Status: Patch Available (was: Open) > Multi-actions in hbase-client could fall in dead loop when region moves. > > > Key: HBASE-13896 > URL: https://issues.apache.org/jira/browse/HBASE-13896 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.13 >Reporter: Victor Xu >Assignee: Victor Xu >Priority: Minor > Attachments: HBASE-13896-0.98-v1.patch > > > The code in AsyncProcess.receiveGlobalFailure() use only one row to update > region cache in hbase-client. When we use HTable.put(List) api to write > some data which are from different regions and some of them are > moved/balanced while writing, the client may fall into a dead loop: > multi-actions fails because some regions moved => update only one region > cache(not the wrong ones) => resubmit => failed again. > It only happens in 0.98 branch, and the master branch is ok. > The patch followed should update all cached region locations when > multi-actions fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13896) Multi-actions in hbase-client could fall in dead loop when region moves.
[ https://issues.apache.org/jira/browse/HBASE-13896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-13896: --- Fix Version/s: 0.98.14 Set fix version > Multi-actions in hbase-client could fall in dead loop when region moves. > > > Key: HBASE-13896 > URL: https://issues.apache.org/jira/browse/HBASE-13896 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.13 >Reporter: Victor Xu >Assignee: Victor Xu >Priority: Minor > Fix For: 0.98.14 > > Attachments: HBASE-13896-0.98-v1.patch > > > The code in AsyncProcess.receiveGlobalFailure() use only one row to update > region cache in hbase-client. When we use HTable.put(List) api to write > some data which are from different regions and some of them are > moved/balanced while writing, the client may fall into a dead loop: > multi-actions fails because some regions moved => update only one region > cache(not the wrong ones) => resubmit => failed again. > It only happens in 0.98 branch, and the master branch is ok. > The patch followed should update all cached region locations when > multi-actions fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13896) Multi-actions in hbase-client could fall in dead loop when region moves.
[ https://issues.apache.org/jira/browse/HBASE-13896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-13896: --- Status: Open (was: Patch Available) Pending test. > Multi-actions in hbase-client could fall in dead loop when region moves. > > > Key: HBASE-13896 > URL: https://issues.apache.org/jira/browse/HBASE-13896 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.13 >Reporter: Victor Xu >Assignee: Victor Xu >Priority: Minor > Fix For: 0.98.14 > > Attachments: HBASE-13896-0.98-v1.patch > > > The code in AsyncProcess.receiveGlobalFailure() use only one row to update > region cache in hbase-client. When we use HTable.put(List) api to write > some data which are from different regions and some of them are > moved/balanced while writing, the client may fall into a dead loop: > multi-actions fails because some regions moved => update only one region > cache(not the wrong ones) => resubmit => failed again. > It only happens in 0.98 branch, and the master branch is ok. > The patch followed should update all cached region locations when > multi-actions fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
