[jira] [Updated] (ZOOKEEPER-3270) Publish metrics for connected clients with user stats
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Appavoo updated ZOOKEEPER-3270: -- Description: There are metrics being published for connected clients. But if we want to find why connection count went up or down, it would be better to expose connections per user stats. (i.e. Some auth info for the connection) Introduce new `clnt` command which is similar to `cons` except this also displays the user-agent to identify the type of client used to connect. List full connection/session details for all clients connected to this server. Includes information on numbers of packets received/sent, session id, operation latencies, last operation performed, user-agent, etc... was:There are metrics being published for connected clients. But if we want to find why connection count went up or down, it would be better to expose connections per user stats. (i.e. Some auth info for the connection) > Publish metrics for connected clients with user stats > - > > Key: ZOOKEEPER-3270 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3270 > Project: ZooKeeper > Issue Type: New Feature > Components: other >Reporter: Dinesh Appavoo >Assignee: Dinesh Appavoo >Priority: Major > Labels: features > > There are metrics being published for connected clients. But if we want to > find why connection count went up or down, it would be better to expose > connections per user stats. (i.e. Some auth info for the connection) > Introduce new `clnt` command which is similar to `cons` except this also > displays the user-agent to identify the type of client used to connect. List > full connection/session details for all clients connected to this server. > Includes information on numbers of packets received/sent, session id, > operation latencies, last operation performed, user-agent, etc... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3270) Publish metrics for connected clients with user stats
Dinesh Appavoo created ZOOKEEPER-3270: - Summary: Publish metrics for connected clients with user stats Key: ZOOKEEPER-3270 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3270 Project: ZooKeeper Issue Type: New Feature Components: other Reporter: Dinesh Appavoo There are metrics being published for connected clients. But if we want to find why connection count went up or down, it would be better to expose connections per user stats. (i.e. Some auth info for the connection) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ZOOKEEPER-3270) Publish metrics for connected clients with user stats
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Appavoo reassigned ZOOKEEPER-3270: - Assignee: Dinesh Appavoo > Publish metrics for connected clients with user stats > - > > Key: ZOOKEEPER-3270 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3270 > Project: ZooKeeper > Issue Type: New Feature > Components: other >Reporter: Dinesh Appavoo >Assignee: Dinesh Appavoo >Priority: Major > Labels: features > > There are metrics being published for connected clients. But if we want to > find why connection count went up or down, it would be better to expose > connections per user stats. (i.e. Some auth info for the connection) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3247) New lest admin command to get leader election time
Dinesh Appavoo created ZOOKEEPER-3247: - Summary: New lest admin command to get leader election time Key: ZOOKEEPER-3247 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3247 Project: ZooKeeper Issue Type: New Feature Components: leaderElection Reporter: Dinesh Appavoo Add lest admin command to get the last leader election time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3246) Publish more stats when learner gets a diff, full snapshot, or does a truncate when it connects with the leader
Dinesh Appavoo created ZOOKEEPER-3246: - Summary: Publish more stats when learner gets a diff, full snapshot, or does a truncate when it connects with the leader Key: ZOOKEEPER-3246 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3246 Project: ZooKeeper Issue Type: New Feature Components: other Reporter: Dinesh Appavoo Problem There is no way to currently tell whether a learner gets a diff or full snapshot, or does a truncate when it connects with the leader, also how long syncing with the leader takes. There is no explicit and general indicator of how often a learner has to connect to a leader without greping through zookeeper.log Solution Start tracking and exporting the following three items: * counter incremented each time a learner sync's with a leader * the type of sync that was needed * how long the sync took -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3241) Update C client for the new getEphemerals api
Dinesh Appavoo created ZOOKEEPER-3241: - Summary: Update C client for the new getEphemerals api Key: ZOOKEEPER-3241 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3241 Project: ZooKeeper Issue Type: New Feature Components: c client Reporter: Dinesh Appavoo There is as new api `getEphemerals()` [https://github.com/apache/zookeeper/pull/735] being introduced in Zookeeper server. Update C client for the API with different parameters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ZOOKEEPER-3209) New `getEphemerals` api to get all the ephemeral nodes created by the session
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Appavoo reassigned ZOOKEEPER-3209: - Assignee: Dinesh Appavoo > New `getEphemerals` api to get all the ephemeral nodes created by the session > - > > Key: ZOOKEEPER-3209 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3209 > Project: ZooKeeper > Issue Type: New Feature > Components: other >Reporter: Dinesh Appavoo >Assignee: Dinesh Appavoo >Priority: Major > Labels: features, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > New API `getEphemerals()` to get all the ephemeral nodes created by the > session by providing the prefix path. > * get the prefix path as a input parameter and return a list of string > (ephemeral nodes) > * If the prefix path is `/` return all the ephemeral nodes created by the > session > * Provide synchronous and asynchronous API's with same functionality -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-3209) New `getEphemerals` api to get all the ephemeral nodes created by the session
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Appavoo updated ZOOKEEPER-3209: -- Summary: New `getEphemerals` api to get all the ephemeral nodes created by the session (was: New `getEphemerals` api to get all the ephemeral nodes created by a session) > New `getEphemerals` api to get all the ephemeral nodes created by the session > - > > Key: ZOOKEEPER-3209 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3209 > Project: ZooKeeper > Issue Type: New Feature > Components: other >Reporter: Dinesh Appavoo >Priority: Major > Labels: features > > New API `getEphemerals()` to get all the ephemeral nodes created by the > session by providing the prefix path. > * get the prefix path as a input parameter and return a list of string > (ephemeral nodes) > * If the prefix path is `/` return all the ephemeral nodes created by the > session > * Provide synchronous and asynchronous API's with same functionality -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3209) New `getEphemerals` api to get all the ephemeral nodes created by a session
Dinesh Appavoo created ZOOKEEPER-3209: - Summary: New `getEphemerals` api to get all the ephemeral nodes created by a session Key: ZOOKEEPER-3209 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3209 Project: ZooKeeper Issue Type: New Feature Components: other Reporter: Dinesh Appavoo New API `getEphemerals()` to get all the ephemeral nodes created by the session by providing the prefix path. * get the prefix path as a input parameter and return a list of string (ephemeral nodes) * If the prefix path is `/` return all the ephemeral nodes created by the session * Provide synchronous and asynchronous API's with same functionality -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ZOOKEEPER-3190) Spell check on the Zookeeper server files
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Appavoo updated ZOOKEEPER-3190: -- Summary: Spell check on the Zookeeper server files (was: Spell check the Zookeeper server files) > Spell check on the Zookeeper server files > - > > Key: ZOOKEEPER-3190 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3190 > Project: ZooKeeper > Issue Type: Improvement > Components: documentation, other >Reporter: Dinesh Appavoo >Priority: Minor > Labels: newbie > > This JIRA is to do spell check on the zookeeper server files [ > zookeeper/zookeeper-server/src/main/java/org/apache/zookeeper/server ]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ZOOKEEPER-3190) Spell check the Zookeeper server files
Dinesh Appavoo created ZOOKEEPER-3190: - Summary: Spell check the Zookeeper server files Key: ZOOKEEPER-3190 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3190 Project: ZooKeeper Issue Type: Improvement Components: documentation, other Reporter: Dinesh Appavoo This JIRA is to do spell check on the zookeeper server files [ zookeeper/zookeeper-server/src/main/java/org/apache/zookeeper/server ]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ZOOKEEPER-2925) ZooKeeper server fails to start on first-startup due to race to create dataDir & snapDir
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653928#comment-16653928
]
Dinesh Appavoo commented on ZOOKEEPER-2925:
---
Thank you for the warm welcome [~andorm] and [~arshad.mohammad]. I didn't try
to reproduce it yet. I was looking for starter tickets and I thought it would
be a good start. I will try to reproduce it. Also feel free to tag me in any
newbie ticket you think it would be a good starter for me. That would be really
helpful. Thanks!
> ZooKeeper server fails to start on first-startup due to race to create
> dataDir & snapDir
>
>
> Key: ZOOKEEPER-2925
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2925
> Project: ZooKeeper
> Issue Type: Bug
> Components: other
>Affects Versions: 3.4.6
>Reporter: Robert P. Thille
>Priority: Major
> Labels: easyfix, newbie, patch
> Fix For: 3.4.10
>
> Attachments: ZOOKEEPER-2925.patch
>
>
> Due to two threads trying to create the dataDir and snapDir, and the
> java.io.File.mkdirs() call returning false both for errors and for the
> directory already existing, sometimes ZooKeeper will fail to start with the
> following stack trace:
> {noformat}
> 2017-10-25 22:30:40,069 [myid:] - INFO [main:ZooKeeperServerMain@95] -
> Starting server
> 2017-10-25 22:30:40,075 [myid:] - INFO [main:Environment@100] - Server
> environment:zookeeper.version=3.4.6-mdavis8efb625--1, built on 10/25/2017
> 01:12 GMT
> [ More 'Server environment:blah blah blah' messages trimmed]
> 2017-10-25 22:30:40,077 [myid:] - INFO [main:Environment@100] - Server
> environment:user.dir=/
> 2017-10-25 22:30:40,081 [myid:] - ERROR [main:ZooKeeperServerMain@63] -
> Unexpected exception, exiting abnormally
> java.io.IOException: Unable to create data directory /bp2/data/version-2
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.(FileTxnSnapLog.java:85)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:104)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(ZooKeeperServerMain.java:86)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.java:52)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:116)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:78)
> 2017-10-25 22:30:40,085 [myid:] - INFO
> [PurgeTask:DatadirCleanupManager$PurgeTask@144] - Purge task completed.
> {noformat}
> this is caused by the QuorumPeerMain thread and the PurgeTask thread both
> competing to create the directories.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (ZOOKEEPER-2925) ZooKeeper server fails to start on first-startup due to race to create dataDir & snapDir
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652716#comment-16652716
]
Dinesh Appavoo edited comment on ZOOKEEPER-2925 at 10/17/18 12:24 AM:
--
Looks like this issue is not addressed yet. And this seems a good starter
ticket for me since I am trying to involve in the community, I can make a pull
request if there is no objection. Thanks! cc: [~arshad.mohammad] [~rthille]
was (Author: dineshappavoo):
Looks like this issue is not addressed yet. And this seems a good starter
ticket, I will make a pull request if there is no objection. cc:
[~arshad.mohammad] [~rthille]
> ZooKeeper server fails to start on first-startup due to race to create
> dataDir & snapDir
>
>
> Key: ZOOKEEPER-2925
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2925
> Project: ZooKeeper
> Issue Type: Bug
> Components: other
>Affects Versions: 3.4.6
>Reporter: Robert P. Thille
>Priority: Major
> Labels: easyfix, newbie, patch
> Fix For: 3.4.10
>
> Attachments: ZOOKEEPER-2925.patch
>
>
> Due to two threads trying to create the dataDir and snapDir, and the
> java.io.File.mkdirs() call returning false both for errors and for the
> directory already existing, sometimes ZooKeeper will fail to start with the
> following stack trace:
> {noformat}
> 2017-10-25 22:30:40,069 [myid:] - INFO [main:ZooKeeperServerMain@95] -
> Starting server
> 2017-10-25 22:30:40,075 [myid:] - INFO [main:Environment@100] - Server
> environment:zookeeper.version=3.4.6-mdavis8efb625--1, built on 10/25/2017
> 01:12 GMT
> [ More 'Server environment:blah blah blah' messages trimmed]
> 2017-10-25 22:30:40,077 [myid:] - INFO [main:Environment@100] - Server
> environment:user.dir=/
> 2017-10-25 22:30:40,081 [myid:] - ERROR [main:ZooKeeperServerMain@63] -
> Unexpected exception, exiting abnormally
> java.io.IOException: Unable to create data directory /bp2/data/version-2
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.(FileTxnSnapLog.java:85)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:104)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(ZooKeeperServerMain.java:86)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.java:52)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:116)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:78)
> 2017-10-25 22:30:40,085 [myid:] - INFO
> [PurgeTask:DatadirCleanupManager$PurgeTask@144] - Purge task completed.
> {noformat}
> this is caused by the QuorumPeerMain thread and the PurgeTask thread both
> competing to create the directories.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ZOOKEEPER-2925) ZooKeeper server fails to start on first-startup due to race to create dataDir & snapDir
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652716#comment-16652716
]
Dinesh Appavoo commented on ZOOKEEPER-2925:
---
Looks like this issue is not addressed yet. And this seems a good starter
ticket, I will make a pull request if there is no objection. cc:
[~arshad.mohammad] [~rthille]
> ZooKeeper server fails to start on first-startup due to race to create
> dataDir & snapDir
>
>
> Key: ZOOKEEPER-2925
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2925
> Project: ZooKeeper
> Issue Type: Bug
> Components: other
>Affects Versions: 3.4.6
>Reporter: Robert P. Thille
>Priority: Major
> Labels: easyfix, newbie, patch
> Fix For: 3.4.10
>
> Attachments: ZOOKEEPER-2925.patch
>
>
> Due to two threads trying to create the dataDir and snapDir, and the
> java.io.File.mkdirs() call returning false both for errors and for the
> directory already existing, sometimes ZooKeeper will fail to start with the
> following stack trace:
> {noformat}
> 2017-10-25 22:30:40,069 [myid:] - INFO [main:ZooKeeperServerMain@95] -
> Starting server
> 2017-10-25 22:30:40,075 [myid:] - INFO [main:Environment@100] - Server
> environment:zookeeper.version=3.4.6-mdavis8efb625--1, built on 10/25/2017
> 01:12 GMT
> [ More 'Server environment:blah blah blah' messages trimmed]
> 2017-10-25 22:30:40,077 [myid:] - INFO [main:Environment@100] - Server
> environment:user.dir=/
> 2017-10-25 22:30:40,081 [myid:] - ERROR [main:ZooKeeperServerMain@63] -
> Unexpected exception, exiting abnormally
> java.io.IOException: Unable to create data directory /bp2/data/version-2
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.(FileTxnSnapLog.java:85)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:104)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(ZooKeeperServerMain.java:86)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.java:52)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:116)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:78)
> 2017-10-25 22:30:40,085 [myid:] - INFO
> [PurgeTask:DatadirCleanupManager$PurgeTask@144] - Purge task completed.
> {noformat}
> this is caused by the QuorumPeerMain thread and the PurgeTask thread both
> competing to create the directories.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
