Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
0.95.2
-
None
-
Reviewed
Description
The tests are done with this settings:
conf.setInt("hbase.master.assignment.timeoutmonitor.period", 2000);
conf.setInt("hbase.master.assignment.timeoutmonitor.timeout", 4000);
As a results:
1) some tests seems to work, but in real life, the recovery would take 5 minutes or more, as in production there always higher. So we don't see the real issues.
2) The tests include specific cases that should not happen in production. It works because the timeout catches everything, but these scenarios do not need to be optimized, as they cannot happen.
Attachments
Attachments
Issue Links
- is required by
-
HBASE-7247 Assignment performances decreased by 50% because of regionserver.OpenRegionHandler#tickleOpening
- Closed
-
HBASE-7327 Assignment Timeouts: Remove the code from the master
- Closed
- relates to
-
HBASE-5843 Improve HBase MTTR - Mean Time To Recover
- Closed
- requires
-
HBASE-7390 Add extra test cases for assignement on the region server and fix the related issues
- Closed