[jira] [Commented] (ZOOKEEPER-102) Need to replace Jute with supported code
[ https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858679#comment-13858679 ] Leader Ni commented on ZOOKEEPER-102: - So, how about avro now in hadoop，and any paln to replace jute? Need to replace Jute with supported code Key: ZOOKEEPER-102 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-102 Project: ZooKeeper Issue Type: Improvement Reporter: Benjamin Reed ZooKeeper currently uses Jute to serialize objects to put on the wire and on disk. We pulled Jute out of Hadoop and added a C binding. Both versions of Jute have evolved (although Hadoop still doesn't have a C binding). It would be nice to use a more standard serialization library. Some options include Thrift or Google's protocol buffers. Our main requirements would be Java and C bindings and good performance. (For example, serializing to XML would give us incredibly bad performance and would not be acceptible!) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (ZOOKEEPER-1804) Stat the realtime tps of zookeepr server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1804: - Description: At this time, we assessed whether zookeeper supports some business scenarios, always use the number of subscribers, or to assess the number of clients。 You konw, some times, many client connection with zookeeper, but do noting, and the onthers do complex business logic。 So，we must stat the realtime tps of zookeepr。 [-Solution---] Solution1: If you only want to know the real time transaction processed, you can use the patch ZOOKEEPER-1804.patch. Solution2: If you also want to know how client use zookeeper, and the real time r/w ps of each zookeeper client, you can use the patch ZOOKEEPER-1804-2.patch use java properties: -Dserver_process_stats=true to open the function. Sample: $echo rwps|nc localhost 2181 RealTime R/W Statistics: getChildren2: 0.5994005994005994 createSession: 1.6983016983016983 closeSession: 0.999000999000999 setData: 110.18981018981019 setWatches: 129.17082917082917 getChildren: 68.83116883116884 delete: 19.980019980019982 create: 22.27772227772228 exists: 1806.2937062937062 getDate: 729.5704295704296 was: At this time, we assessed whether zookeeper supports some business scenarios, always use the number of subscribers, or to assess the number of clients。 You konw, some times, many client connection with zookeeper, but do noting, and the onthers do complex business logic。 So，we must stat the realtime tps of zookeepr。 [-Solution---] Solution1: If you only want to know the real time transaction processed, you can use the patch ZOOKEEPER-1804.patch. Solution2: If you also want to know how client use zookeeper, and the real time r/w ps of each zookeeper client, you can use the patch ZOOKEEPER-1804-2.patch Sample: $echo rwps|nc localhost 2181 RealTime R/W Statistics: getChildren2: 0.5994005994005994 createSession: 1.6983016983016983 closeSession: 0.999000999000999 setData: 110.18981018981019 setWatches: 129.17082917082917 getChildren: 68.83116883116884 delete: 19.980019980019982 create: 22.27772227772228 exists: 1806.2937062937062 getDate: 729.5704295704296 Stat the realtime tps of zookeepr server Key: ZOOKEEPER-1804 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1804 Project: ZooKeeper Issue Type: Improvement Components: server Reporter: Leader Ni Assignee: Leader Ni Attachments: ZOOKEEPER-1804.patch At this time, we assessed whether zookeeper supports some business scenarios, always use the number of subscribers, or to assess the number of clients。 You konw, some times, many client connection with zookeeper, but do noting, and the onthers do complex business logic。 So，we must stat the realtime tps of zookeepr。 [-Solution---] Solution1: If you only want to know the real time transaction processed, you can use the patch ZOOKEEPER-1804.patch. Solution2: If you also want to know how client use zookeeper, and the real time r/w ps of each zookeeper client, you can use the patch ZOOKEEPER-1804-2.patch use java properties: -Dserver_process_stats=true to open the function. Sample: $echo rwps|nc localhost 2181 RealTime R/W Statistics: getChildren2: 0.5994005994005994 createSession: 1.6983016983016983 closeSession: 0.999000999000999 setData: 110.18981018981019 setWatches: 129.17082917082917 getChildren: 68.83116883116884 delete: 19.980019980019982 create: 22.27772227772228 exists: 1806.2937062937062 getDate: 729.5704295704296 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1804) Stat the realtime tps of zookeepr server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1804: - Attachment: ZOOKEEPER-1804-2.patch Stat the realtime tps of zookeepr server Key: ZOOKEEPER-1804 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1804 Project: ZooKeeper Issue Type: Improvement Components: server Reporter: Leader Ni Assignee: Leader Ni Attachments: ZOOKEEPER-1804-2.patch, ZOOKEEPER-1804.patch At this time, we assessed whether zookeeper supports some business scenarios, always use the number of subscribers, or to assess the number of clients。 You konw, some times, many client connection with zookeeper, but do noting, and the onthers do complex business logic。 So，we must stat the realtime tps of zookeepr。 [-Solution---] Solution1: If you only want to know the real time transaction processed, you can use the patch ZOOKEEPER-1804.patch. Solution2: If you also want to know how client use zookeeper, and the real time r/w ps of each zookeeper client, you can use the patch ZOOKEEPER-1804-2.patch use java properties: -Dserver_process_stats=true to open the function. Sample: $echo rwps|nc localhost 2181 RealTime R/W Statistics: getChildren2: 0.5994005994005994 createSession: 1.6983016983016983 closeSession: 0.999000999000999 setData: 110.18981018981019 setWatches: 129.17082917082917 getChildren: 68.83116883116884 delete: 19.980019980019982 create: 22.27772227772228 exists: 1806.2937062937062 getDate: 729.5704295704296 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1804) Stat the realtime tps of zookeepr server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811080#comment-13811080 ] Leader Ni commented on ZOOKEEPER-1804: -- patch2 sample $echo rwps|nc localhost 2181 RealTime R/W Statistics: getChildren2:0.5994005994005994 createSession: 1.6983016983016983 closeSession:0.999000999000999 setData:110.18981018981019 setWatches: 129.17082917082917 getChildren: 68.83116883116884 delete: 19.980019980019982 create: 22.27772227772228 exists:1806.2937062937062 getDate: 729.5704295704296 Stat the realtime tps of zookeepr server Key: ZOOKEEPER-1804 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1804 Project: ZooKeeper Issue Type: Improvement Components: server Reporter: Leader Ni Assignee: Leader Ni Attachments: ZOOKEEPER-1804.patch At this time, we assessed whether zookeeper supports some business scenarios, always use the number of subscribers, or to assess the number of clients。 You konw, some times, many client connection with zookeeper, but do noting, and the onthers do complex business logic。 So，we must stat the realtime tps of zookeepr。 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1804) Stat the realtime tps of zookeepr server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1804: - Description: At this time, we assessed whether zookeeper supports some business scenarios, always use the number of subscribers, or to assess the number of clients。 You konw, some times, many client connection with zookeeper, but do noting, and the onthers do complex business logic。 So，we must stat the realtime tps of zookeepr。 [-Solution---] Solution1: If you only want to know the real time transaction processed, you can use the patch ZOOKEEPER-1804.patch. Solution2: If you also want to know how client use zookeeper, and the real time r/w ps of each zookeeper client, you can use the patch ZOOKEEPER-1804-2.patch Sample: $echo rwps|nc localhost 2181 RealTime R/W Statistics: getChildren2: 0.5994005994005994 createSession: 1.6983016983016983 closeSession: 0.999000999000999 setData: 110.18981018981019 setWatches: 129.17082917082917 getChildren: 68.83116883116884 delete: 19.980019980019982 create: 22.27772227772228 exists: 1806.2937062937062 getDate: 729.5704295704296 was: At this time, we assessed whether zookeeper supports some business scenarios, always use the number of subscribers, or to assess the number of clients。 You konw, some times, many client connection with zookeeper, but do noting, and the onthers do complex business logic。 So，we must stat the realtime tps of zookeepr。 Stat the realtime tps of zookeepr server Key: ZOOKEEPER-1804 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1804 Project: ZooKeeper Issue Type: Improvement Components: server Reporter: Leader Ni Assignee: Leader Ni Attachments: ZOOKEEPER-1804.patch At this time, we assessed whether zookeeper supports some business scenarios, always use the number of subscribers, or to assess the number of clients。 You konw, some times, many client connection with zookeeper, but do noting, and the onthers do complex business logic。 So，we must stat the realtime tps of zookeepr。 [-Solution---] Solution1: If you only want to know the real time transaction processed, you can use the patch ZOOKEEPER-1804.patch. Solution2: If you also want to know how client use zookeeper, and the real time r/w ps of each zookeeper client, you can use the patch ZOOKEEPER-1804-2.patch Sample: $echo rwps|nc localhost 2181 RealTime R/W Statistics: getChildren2: 0.5994005994005994 createSession: 1.6983016983016983 closeSession: 0.999000999000999 setData: 110.18981018981019 setWatches: 129.17082917082917 getChildren: 68.83116883116884 delete: 19.980019980019982 create: 22.27772227772228 exists: 1806.2937062937062 getDate: 729.5704295704296 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (ZOOKEEPER-1804) Stat the realtime tps of zookeepr server
Leader Ni created ZOOKEEPER-1804: Summary: Stat the realtime tps of zookeepr server Key: ZOOKEEPER-1804 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1804 Project: ZooKeeper Issue Type: Improvement Components: server Reporter: Leader Ni Assignee: Leader Ni At this time, we assessed whether zookeeper supports some business scenarios, always use the number of subscribers, or to assess the number of clients。 You konw, some times, many client connection with zookeeper, but do noting, and the onthers do complex business logic。 So，we must stat the realtime tps of zookeepr。 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (ZOOKEEPER-1803) Add description for pzxid in programmer's guide.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13806074#comment-13806074 ] Leader Ni commented on ZOOKEEPER-1803: -- pzxid：The zxid of the change that last modified children of this znode. Add description for pzxid in programmer's guide. Key: ZOOKEEPER-1803 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1803 Project: ZooKeeper Issue Type: Improvement Components: documentation Reporter: Leader Ni Assignee: Leader Ni Priority: Trivial The Stat（org.apache.zookeeper.data.Stat） Structures has the filed pzxid, but no document about it in programmer's guide（http://zookeeper.apache.org/doc/r3.4.3/zookeeperProgrammers.html#sc_zkStatStructure） -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1803) Add description for pzxid in programmer's guide.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1803: - Attachment: zookeeperProgrammers.html.patch Add description for pzxid in zookeeperProgrammers.html Add description for pzxid in programmer's guide. Key: ZOOKEEPER-1803 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1803 Project: ZooKeeper Issue Type: Improvement Components: documentation Reporter: Leader Ni Assignee: Leader Ni Priority: Trivial Attachments: zookeeperProgrammers.html.patch The Stat（org.apache.zookeeper.data.Stat） Structures has the filed pzxid, but no document about it in programmer's guide（http://zookeeper.apache.org/doc/r3.4.3/zookeeperProgrammers.html#sc_zkStatStructure） -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (ZOOKEEPER-1480) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1480: - Attachment: (was: getCurrentZooKeeperAddr_for_3.3.3.patch) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error Key: ZOOKEEPER-1480 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1480 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.3.3 Reporter: Leader Ni Assignee: Leader Ni Labels: client, getCurrentZooKeeperAddr Fix For: 3.4.4, 3.5.0 Attachments: getCurrentZooKeeperAddr_for_branch3.4.patch When zookeeper occur an unexpected error( Not SessionExpiredException, SessionTimeoutException and EndOfStreamException), ClientCnxn(1161) will log such as the formart Session 0x for server null, unexpected error, closing socket connection and attempting reconnect . The log at line 1161 in zookeeper-3.3.3 We found that, zookeeper use ((SocketChannel)sockKey.channel()).socket().getRemoteSocketAddress() to get zookeeper addr. But,Sometimes, it logs Session 0x for server null, you know, if log null, developer can't determine the current zookeeper addr that client is connected or connecting. I add a method in Class SendThread:InetSocketAddress org.apache.zookeeper.ClientCnxn.SendThread.getCurrentZooKeeperAddr(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1480) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1480: - Attachment: (was: getCurrentZooKeeperAddr_for_trunk.patch) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error Key: ZOOKEEPER-1480 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1480 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.3.3 Reporter: Leader Ni Assignee: Leader Ni Labels: client, getCurrentZooKeeperAddr Fix For: 3.4.4, 3.5.0 Attachments: getCurrentZooKeeperAddr_for_branch3.4.patch When zookeeper occur an unexpected error( Not SessionExpiredException, SessionTimeoutException and EndOfStreamException), ClientCnxn(1161) will log such as the formart Session 0x for server null, unexpected error, closing socket connection and attempting reconnect . The log at line 1161 in zookeeper-3.3.3 We found that, zookeeper use ((SocketChannel)sockKey.channel()).socket().getRemoteSocketAddress() to get zookeeper addr. But,Sometimes, it logs Session 0x for server null, you know, if log null, developer can't determine the current zookeeper addr that client is connected or connecting. I add a method in Class SendThread:InetSocketAddress org.apache.zookeeper.ClientCnxn.SendThread.getCurrentZooKeeperAddr(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1480) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1480: - Attachment: getCurrentZooKeeperAddr_for_3.4.3.patch ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error Key: ZOOKEEPER-1480 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1480 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.4.3 Reporter: Leader Ni Assignee: Leader Ni Labels: client, getCurrentZooKeeperAddr Fix For: 3.5.0 Attachments: getCurrentZooKeeperAddr_for_3.4.3.patch, getCurrentZooKeeperAddr_for_branch3.4.patch When zookeeper occur an unexpected error( Not SessionExpiredException, SessionTimeoutException and EndOfStreamException), ClientCnxn(1161) will log such as the formart Session 0x for server null, unexpected error, closing socket connection and attempting reconnect . The log at line 1161 in zookeeper-3.3.3 We found that, zookeeper use ((SocketChannel)sockKey.channel()).socket().getRemoteSocketAddress() to get zookeeper addr. But,Sometimes, it logs Session 0x for server null, you know, if log null, developer can't determine the current zookeeper addr that client is connected or connecting. I add a method in Class SendThread:InetSocketAddress org.apache.zookeeper.ClientCnxn.SendThread.getCurrentZooKeeperAddr(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1543) Bad sessionId/password combo should return auth failure
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13447267#comment-13447267 ] Leader Ni commented on ZOOKEEPER-1543: -- You mean zookeeper need to differentiate AUTH_FAILURE from SESSION_EXPIRED？ We know, zookeeper will have two password, one is in client connection, and another is is digest auth check. The first password may the thing you said. You know, usually, we will not change this password. So, What's the meanning of telling client the AUTH_FAILURE. And the second password---the password in digest, i'm sure server will tell client the auth_failure. Bad sessionId/password combo should return auth failure --- Key: ZOOKEEPER-1543 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1543 Project: ZooKeeper Issue Type: Improvement Components: server Affects Versions: 3.4.3, 3.3.6, 3.5.0 Environment: All Reporter: Ben Bangert When connecting to a server with a valid session id, but invalid password, Zookeeper disconnects with a SESSION_EXPIRED error. This is blatantly false, its actually the wrong password. Returning a SESSION_EXPIRED in this case is also not documented anywhere. This makes debugging this issue an absolute nightmare, since the server has already lead you down the wrong track (trying to figure out why the session is expired, but it isn't). There's already an AUTH_FAILURE error, why not return that? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1480) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1480: - Attachment: getCurrentZooKeeperAddr_for_trunk.patch getCurrentZooKeeperAddr_for_branch3.4.patch getCurrentZooKeeperAddr_for_3.3.3.patch ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error Key: ZOOKEEPER-1480 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1480 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.3.3 Reporter: Leader Ni Assignee: Leader Ni Labels: client, getCurrentZooKeeperAddr Fix For: 3.4.4, 3.5.0 Attachments: getCurrentZooKeeperAddr.patch, getCurrentZooKeeperAddr_for_3.3.3.patch, getCurrentZooKeeperAddr_for_branch3.4.patch, getCurrentZooKeeperAddr_for_trunk.patch When zookeeper occur an unexpected error( Not SessionExpiredException, SessionTimeoutException and EndOfStreamException), ClientCnxn(1161) will log such as the formart Session 0x for server null, unexpected error, closing socket connection and attempting reconnect . The log at line 1161 in zookeeper-3.3.3 We found that, zookeeper use ((SocketChannel)sockKey.channel()).socket().getRemoteSocketAddress() to get zookeeper addr. But,Sometimes, it logs Session 0x for server null, you know, if log null, developer can't determine the current zookeeper addr that client is connected or connecting. I add a method in Class SendThread:InetSocketAddress org.apache.zookeeper.ClientCnxn.SendThread.getCurrentZooKeeperAddr(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1480) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1480: - Attachment: (was: getCurrentZooKeeperAddr.patch) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error Key: ZOOKEEPER-1480 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1480 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.3.3 Reporter: Leader Ni Assignee: Leader Ni Labels: client, getCurrentZooKeeperAddr Fix For: 3.4.4, 3.5.0 Attachments: getCurrentZooKeeperAddr_for_3.3.3.patch, getCurrentZooKeeperAddr_for_branch3.4.patch, getCurrentZooKeeperAddr_for_trunk.patch When zookeeper occur an unexpected error( Not SessionExpiredException, SessionTimeoutException and EndOfStreamException), ClientCnxn(1161) will log such as the formart Session 0x for server null, unexpected error, closing socket connection and attempting reconnect . The log at line 1161 in zookeeper-3.3.3 We found that, zookeeper use ((SocketChannel)sockKey.channel()).socket().getRemoteSocketAddress() to get zookeeper addr. But,Sometimes, it logs Session 0x for server null, you know, if log null, developer can't determine the current zookeeper addr that client is connected or connecting. I add a method in Class SendThread:InetSocketAddress org.apache.zookeeper.ClientCnxn.SendThread.getCurrentZooKeeperAddr(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (ZOOKEEPER-1480) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error
Leader Ni created ZOOKEEPER-1480: Summary: ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error Key: ZOOKEEPER-1480 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1480 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.3.3 Reporter: Leader Ni Assignee: Leader Ni Fix For: 3.3.6 When zookeeper occur an unexpected error( Not SessionExpiredException, SessionTimeoutException and EndOfStreamException), ClientCnxn(1161) will log such as the formart Session 0x for server null, unexpected error, closing socket connection and attempting reconnect . The log at line 1161 in zookeeper-3.3.3 We found that, sometimes, it logs Session 0x for server null, you know, if log null, developer can't determine the current zookeeper addr that client is connected or connecting. I add a method in Class SendThread:InetSocketAddress org.apache.zookeeper.ClientCnxn.SendThread.getCurrentZooKeeperAddr(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1480) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1480: - Attachment: getCurrentZooKeeperAddr.path ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error Key: ZOOKEEPER-1480 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1480 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.3.3 Reporter: Leader Ni Assignee: Leader Ni Labels: client, getCurrentZooKeeperAddr Fix For: 3.3.6 Attachments: getCurrentZooKeeperAddr.path When zookeeper occur an unexpected error( Not SessionExpiredException, SessionTimeoutException and EndOfStreamException), ClientCnxn(1161) will log such as the formart Session 0x for server null, unexpected error, closing socket connection and attempting reconnect . The log at line 1161 in zookeeper-3.3.3 We found that, zookeeper use ((SocketChannel)sockKey.channel()).socket().getRemoteSocketAddress() to get zookeeper addr. But,Sometimes, it logs Session 0x for server null, you know, if log null, developer can't determine the current zookeeper addr that client is connected or connecting. I add a method in Class SendThread:InetSocketAddress org.apache.zookeeper.ClientCnxn.SendThread.getCurrentZooKeeperAddr(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1480) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1480: - Attachment: (was: getCurrentZooKeeperAddr.path) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error Key: ZOOKEEPER-1480 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1480 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.3.3 Reporter: Leader Ni Assignee: Leader Ni Labels: client, getCurrentZooKeeperAddr Fix For: 3.3.6 Attachments: getCurrentZooKeeperAddr.patch When zookeeper occur an unexpected error( Not SessionExpiredException, SessionTimeoutException and EndOfStreamException), ClientCnxn(1161) will log such as the formart Session 0x for server null, unexpected error, closing socket connection and attempting reconnect . The log at line 1161 in zookeeper-3.3.3 We found that, zookeeper use ((SocketChannel)sockKey.channel()).socket().getRemoteSocketAddress() to get zookeeper addr. But,Sometimes, it logs Session 0x for server null, you know, if log null, developer can't determine the current zookeeper addr that client is connected or connecting. I add a method in Class SendThread:InetSocketAddress org.apache.zookeeper.ClientCnxn.SendThread.getCurrentZooKeeperAddr(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1480) ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leader Ni updated ZOOKEEPER-1480: - Attachment: getCurrentZooKeeperAddr.patch ClientCnxn(1161) can't get the current zk server add, so that - Session 0x for server null, unexpected error Key: ZOOKEEPER-1480 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1480 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.3.3 Reporter: Leader Ni Assignee: Leader Ni Labels: client, getCurrentZooKeeperAddr Fix For: 3.3.6 Attachments: getCurrentZooKeeperAddr.patch When zookeeper occur an unexpected error( Not SessionExpiredException, SessionTimeoutException and EndOfStreamException), ClientCnxn(1161) will log such as the formart Session 0x for server null, unexpected error, closing socket connection and attempting reconnect . The log at line 1161 in zookeeper-3.3.3 We found that, zookeeper use ((SocketChannel)sockKey.channel()).socket().getRemoteSocketAddress() to get zookeeper addr. But,Sometimes, it logs Session 0x for server null, you know, if log null, developer can't determine the current zookeeper addr that client is connected or connecting. I add a method in Class SendThread:InetSocketAddress org.apache.zookeeper.ClientCnxn.SendThread.getCurrentZooKeeperAddr(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
