[jira] [Commented] (HBASE-19312) Find out why sometimes we need to spend more than one second to get the cluster id

2017-11-21 Thread Duo Zhang (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261835#comment-16261835 ] Duo Zhang commented on HBASE-19312: --- {quote} How much work would this be Duo Zhang (This would be

[jira] [Commented] (HBASE-19312) Find out why sometimes we need to spend more than one second to get the cluster id

2017-11-21 Thread Mike Drob (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261345#comment-16261345 ] Mike Drob commented on HBASE-19312: --- I'm traveling this week but can look at this on Monday at the

[jira] [Commented] (HBASE-19312) Find out why sometimes we need to spend more than one second to get the cluster id

2017-11-21 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261189#comment-16261189 ] stack commented on HBASE-19312: --- bq. then let's drop curator first and implement our own read only

[jira] [Commented] (HBASE-19312) Find out why sometimes we need to spend more than one second to get the cluster id

2017-11-21 Thread Duo Zhang (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260385#comment-16260385 ] Duo Zhang commented on HBASE-19312: --- Filed CURATOR-443 to report the problem. A temporary workaround is

[jira] [Commented] (HBASE-19312) Find out why sometimes we need to spend more than one second to get the cluster id

2017-11-20 Thread Duo Zhang (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260271#comment-16260271 ] Duo Zhang commented on HBASE-19312: --- [~mdrob] hey curator committer, could you please explain this