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

Patrick Hunt updated ZOOKEEPER-64:
----------------------------------

    Attachment: ZOOKEEPER-64.patch

Added logging for the variables listed in the previous comments.

All logging is at INFO level.

In java I added to the client and server, logged once during class loading.
In C I added to the zookeeper_init method, logged once for each call of init.

Notice to reviewers: notice that each data entry is logged with it's own log 
call, rather than logged as a single call (resulting in very long, hard to 
read, line). Also didn't want to output a single log with carriage returns as 
that can be difficult to parse/grep. I think this is the optimum approach.

I also updated the server to add a new "envi" command. Allows querying of same 
data from the command port. Also notice that the docs have been updated as well.



> We should log system env information when intializing client/server
> -------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-64
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-64
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: c client, java client, server
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-64.patch
>
>
> We should log system environment information (as much as possible) during 
> both client & server initialization. This will help with debugging of 
> customer issues.

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

Reply via email to