[
https://issues.apache.org/jira/browse/HBASE-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HBASE-7268:
------------------------------------
Description:
Discovered via HBASE-7250; related to HBASE-5877.
Test is writing from multiple threads.
Server A has region R; client knows that.
R gets moved from A to server B.
B gets killed.
R gets moved by master to server C.
~15 seconds later, client tries to write to it (on A?).
Multiple client threads report from RegionMoved exception processing logic "R
moved from C to B", even though such transition never happened (neither in nor
before the sequence described below), then put fails (it may fail due to
accumulated errors that are not logged, which I am investigating... but the
bogus cache update is there nonwithstanding).
I have a patch but not sure if it works, test still fails locally for yet
unknown reason.
was:
Discovered via HBASE-7250; related to HBASE-5877.
Test is writing from multiple threads.
Server A has region R.
R gets moved from A to server B.
Server B gets killed.
Region gets moved by master to server C.
~15 seconds later, client tries to write to it.
Multiple client threads report "region moved from C to B", even though such
transition never happened (neither in nor before the sequence described below).
I have a patch but not sure if it works, test still fails locally for yet
unknown reason.
> correct local region location cache information can be overwritten w/stale
> information from an old server
> ---------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7268
> URL: https://issues.apache.org/jira/browse/HBASE-7268
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Minor
>
> Discovered via HBASE-7250; related to HBASE-5877.
> Test is writing from multiple threads.
> Server A has region R; client knows that.
> R gets moved from A to server B.
> B gets killed.
> R gets moved by master to server C.
> ~15 seconds later, client tries to write to it (on A?).
> Multiple client threads report from RegionMoved exception processing logic "R
> moved from C to B", even though such transition never happened (neither in
> nor before the sequence described below), then put fails (it may fail due to
> accumulated errors that are not logged, which I am investigating... but the
> bogus cache update is there nonwithstanding).
> I have a patch but not sure if it works, test still fails locally for yet
> unknown reason.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
