You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2008/11/18 19:55:44 UTC

[jira] Created: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters

c client should log an info message in zookeeper_init detailing connection parameters
-------------------------------------------------------------------------------------

                 Key: ZOOKEEPER-225
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225
             Project: Zookeeper
          Issue Type: Improvement
          Components: c client
    Affects Versions: 3.0.0
            Reporter: Patrick Hunt
            Priority: Minor
             Fix For: 3.1.0


I've debugged a few situations where the client connection param was not set properly (even though the user swore that it was). We should log info level message during init to enable us (and user) to easier debug.

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


[jira] Updated: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters

Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt updated ZOOKEEPER-225:
-----------------------------------

    Attachment: ZOOKEEPER-225.patch

This patch adds info logs to both the c and java clients detailing the connection parameters - useful in certain debugging situations.

> c client should log an info message in zookeeper_init detailing connection parameters
> -------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-225
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: c client
>    Affects Versions: 3.0.0, 3.0.1
>            Reporter: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-225.patch
>
>
> I've debugged a few situations where the client connection param was not set properly (even though the user swore that it was). We should log info level message during init to enable us (and user) to easier debug.

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


[jira] Updated: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters

Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar updated ZOOKEEPER-225:
------------------------------------

    Attachment: ZOOKEEPER-225.patch

just reformatted a log line to break it up into 2 lines.

> c client should log an info message in zookeeper_init detailing connection parameters
> -------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-225
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: c client
>    Affects Versions: 3.0.0, 3.0.1
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-225.patch, ZOOKEEPER-225.patch
>
>
> I've debugged a few situations where the client connection param was not set properly (even though the user swore that it was). We should log info level message during init to enable us (and user) to easier debug.

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


[jira] Commented: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656954#action_12656954 ] 

Hudson commented on ZOOKEEPER-225:
----------------------------------

Integrated in ZooKeeper-trunk #174 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/174/])
    

> c client should log an info message in zookeeper_init detailing connection parameters
> -------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-225
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: c client
>    Affects Versions: 3.0.0, 3.0.1
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-225.patch, ZOOKEEPER-225.patch
>
>
> I've debugged a few situations where the client connection param was not set properly (even though the user swore that it was). We should log info level message during init to enable us (and user) to easier debug.

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


[jira] Updated: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters

Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt updated ZOOKEEPER-225:
-----------------------------------

             Assignee: Patrick Hunt
    Affects Version/s: 3.0.1
               Status: Patch Available  (was: Open)

> c client should log an info message in zookeeper_init detailing connection parameters
> -------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-225
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: c client
>    Affects Versions: 3.0.1, 3.0.0
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-225.patch
>
>
> I've debugged a few situations where the client connection param was not set properly (even though the user swore that it was). We should log info level message during init to enable us (and user) to easier debug.

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


[jira] Commented: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters

Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655355#action_12655355 ] 

Mahadev konar commented on ZOOKEEPER-225:
-----------------------------------------

+1 for the patch... its good that you didnt print the passwd :) ... 

> c client should log an info message in zookeeper_init detailing connection parameters
> -------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-225
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: c client
>    Affects Versions: 3.0.0, 3.0.1
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-225.patch
>
>
> I've debugged a few situations where the client connection param was not set properly (even though the user swore that it was). We should log info level message during init to enable us (and user) to easier debug.

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


[jira] Updated: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters

Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar updated ZOOKEEPER-225:
------------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

i just committed this. thanks pat.

> c client should log an info message in zookeeper_init detailing connection parameters
> -------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-225
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: c client
>    Affects Versions: 3.0.0, 3.0.1
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-225.patch, ZOOKEEPER-225.patch
>
>
> I've debugged a few situations where the client connection param was not set properly (even though the user swore that it was). We should log info level message during init to enable us (and user) to easier debug.

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