[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-5075: -- Status: Open (was: Patch Available) > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, Replication, Zookeeper >Affects Versions: 0.90.5 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-shell.patch, > HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- 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-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anonymous updated HBASE-5075: - Affects Version/s: (was: 0.92.1) 0.90.5 Hadoop Flags: Incompatible change Status: Patch Available (was: Reopened) > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, Replication, Zookeeper >Affects Versions: 0.90.5 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-shell.patch, > HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- 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-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiyuan.dai updated HBASE-5075: --- Attachment: HBase-5075-shell.patch > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-shell.patch, > HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiyuan.dai updated HBASE-5075: --- Attachment: (was: HBase-5075-shell.patch) > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-shell.patch, > HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhengBowen updated HBASE-5075: -- Attachment: (was: monitor-daemon.sh) > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-shell.patch, > HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhengBowen updated HBASE-5075: -- Attachment: (was: start-monitors.sh) > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-shell.patch, > HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhengBowen updated HBASE-5075: -- Attachment: (was: stop-monitors.sh) > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-shell.patch, > HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiyuan.dai updated HBASE-5075: --- Attachment: HBase-5075-shell.patch > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-shell.patch, > HBase-5075-src.patch, monitor-daemon.sh, start-monitors.sh, stop-monitors.sh > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhengBowen updated HBASE-5075: -- Attachment: stop-monitors.sh start-monitors.sh monitor-daemon.sh the shell which start&stop monitors. > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-src.patch, > monitor-daemon.sh, start-monitors.sh, stop-monitors.sh > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiyuan.dai updated HBASE-5075: --- Attachment: Degion of Failure Detection.pdf > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: Degion of Failure Detection.pdf, HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiyuan.dai updated HBASE-5075: --- Attachment: HBase-5075-src.patch > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiyuan.dai updated HBASE-5075: --- Attachment: (was: 5075.patch) > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: HBase-5075-src.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhiyuan.dai updated HBASE-5075: --- Attachment: 5075.patch > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: zhiyuan.dai > Fix For: 0.90.5 > > Attachments: 5075.patch > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 代志远 updated HBASE-5075: --- Fix Version/s: 0.90.5 > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: 代志远 > Fix For: 0.90.5 > > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 代志远 updated HBASE-5075: --- Description: regionserver crashed,it is too long time to notify hmaster.when hmaster know regionserver's shutdown,it is long time to fetch the hlog's lease. hbase is a online db, availability is very important. i have a idea to improve availability, monitor node to check regionserver's pid.if this pid not exsits,i think the rs down,i will delete the znode,and force close the hlog file. so the period maybe 100ms. was: regionserver crashed,it is too long time to notify hmaster.when hmaster know regionserver's shutdown,it is long time to fetch the hlog's lease. hbase is a online db,availability is very important. i have a idea to improve availability,mintor node to check regionserver's pid.if this pid notexsits,i think the rs down,i will delete the znode,and force close the hlog file. so the period maybe 100ms. > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: 代志远 > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db, availability is very important. > i have a idea to improve availability, monitor node to check regionserver's > pid.if this pid not exsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5075) regionserver crashed and failover
[ https://issues.apache.org/jira/browse/HBASE-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 代志远 updated HBASE-5075: --- Affects Version/s: (was: 0.90.4) 0.92.1 Fix Version/s: (was: 0.92.1) Summary: regionserver crashed and failover (was: regionserver crashed,and failover) > regionserver crashed and failover > - > > Key: HBASE-5075 > URL: https://issues.apache.org/jira/browse/HBASE-5075 > Project: HBase > Issue Type: Improvement > Components: monitoring, regionserver, replication, zookeeper >Affects Versions: 0.92.1 >Reporter: 代志远 > > regionserver crashed,it is too long time to notify hmaster.when hmaster know > regionserver's shutdown,it is long time to fetch the hlog's lease. > hbase is a online db,availability is very important. > i have a idea to improve availability,mintor node to check regionserver's > pid.if this pid notexsits,i think the rs down,i will delete the znode,and > force close the hlog file. > so the period maybe 100ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
