[jira] Created: (ZOOKEEPER-595) A means of asking quorum what conifguration it is running with

2009-11-24 Thread stack (JIRA)
A means of asking quorum what conifguration it is running with
--

 Key: ZOOKEEPER-595
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-595
 Project: Zookeeper
  Issue Type: Improvement
Reporter: stack


I'd like to ask a running quorum what its configuration is.  I'd want to know 
stuff like session timeout and tick times.

Use case is that in hbase there is no zoo.cfg usually; the configuration is 
manufactured and piped to the starting zk server.  I want to know if all of the 
manufactured config. 'took' or how zk interpreted it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (ZOOKEEPER-587) client should log timeout negotiated with server

2009-11-21 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781074#action_12781074
 ] 

stack commented on ZOOKEEPER-587:
-

If server changes the timeout on the client, yeah, for sure at least log it.  
Good stuff.

 client should log timeout negotiated with server
 

 Key: ZOOKEEPER-587
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-587
 Project: Zookeeper
  Issue Type: Bug
  Components: c client, java client
Affects Versions: 3.2.1
Reporter: Patrick Hunt
 Fix For: 3.3.0


 The ZK client should log the timeout negotiated with the server if the time 
 is different than the timeout parameter specified by the client.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.