[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Resolution: Fixed Fix Version/s: 0.96.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Fix For: 0.96.0 Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch, 7407.v5.patch, 7407.v6.patch, 7407_v7.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Open (was: Patch Available) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch, 7407.v5.patch, 7407.v6.patch, 7407_v7.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Attachment: 7407_v7.patch TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch, 7407.v5.patch, 7407.v6.patch, 7407_v7.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Patch Available (was: Open) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch, 7407.v5.patch, 7407.v6.patch, 7407_v7.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Open (was: Patch Available) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch, 7407.v5.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Attachment: 7407.v6.patch TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch, 7407.v5.patch, 7407.v6.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Patch Available (was: Open) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch, 7407.v5.patch, 7407.v6.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Open (was: Patch Available) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Patch Available (was: Open) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch, 7407.v5.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Attachment: 7407.v5.patch TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch, 7407.v5.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Open (was: Patch Available) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Attachment: 7407.v3.patch TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Patch Available (was: Open) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch, 7407.v3.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Patch Available (was: Open) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v1.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Attachment: 7407.v1.patch TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v1.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Attachment: (was: 7407.v1.patch) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Open (was: Patch Available) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Status: Patch Available (was: Open) TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Attachment: 7407.v2.patch TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Component/s: Region Assignment TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, Region Assignment, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch, 7407.v2.patch 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. -- 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
[jira] [Updated] (HBASE-7407) TestMasterFailover under tests some cases and over tests some others
[ https://issues.apache.org/jira/browse/HBASE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7407: --- Attachment: 7407.v1.patch TestMasterFailover under tests some cases and over tests some others Key: HBASE-7407 URL: https://issues.apache.org/jira/browse/HBASE-7407 Project: HBase Issue Type: Bug Components: master, test Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 7407.v1.patch 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. -- 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
