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

2017-11-22 Thread Duo Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang updated HBASE-19312:
--
Priority: Critical  (was: Blocker)

Seems I misunderstood the sleepFor method in curator, it just sets the sleep 
time instead of actually sleeping so it will not block our threads. Lower to 
critical.

> Find out why sometimes we need to spend more than one second to get the 
> cluster id
> --
>
> Key: HBASE-19312
> URL: https://issues.apache.org/jira/browse/HBASE-19312
> Project: HBase
>  Issue Type: Bug
>  Components: asyncclient, Client, Zookeeper
>Reporter: Duo Zhang
>Priority: Critical
> Fix For: 2.0.0
>
>
> See the discussion in HBASE-19266.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (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:all-tabpanel
 ]

Duo Zhang updated HBASE-19312:
--
 Priority: Blocker  (was: Major)
Fix Version/s: 2.0.0
  Component/s: Zookeeper
   Client
   asyncclient

This is a very critical problem as sleeping in foreground will cause very bad 
performance impact for asynchronous program.

Marked as a blocker for 2.0.0 release. If we can not find a way to purge this 
in curator, then I think we need to drop curator and implement our own read 
only zk client.

Thanks.

> Find out why sometimes we need to spend more than one second to get the 
> cluster id
> --
>
> Key: HBASE-19312
> URL: https://issues.apache.org/jira/browse/HBASE-19312
> Project: HBase
>  Issue Type: Bug
>  Components: asyncclient, Client, Zookeeper
>Reporter: Duo Zhang
>Priority: Blocker
> Fix For: 2.0.0
>
>
> See the discussion in HBASE-19266.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (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:all-tabpanel
 ]

Duo Zhang updated HBASE-19312:
--
Description: See the discussion in HBASE-19266.

> Find out why sometimes we need to spend more than one second to get the 
> cluster id
> --
>
> Key: HBASE-19312
> URL: https://issues.apache.org/jira/browse/HBASE-19312
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>
> See the discussion in HBASE-19266.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)