[jira] [Commented] (ZOOKEEPER-1045) Quorum Peer mutual authentication
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085696#comment-15085696
]
Rakesh R commented on ZOOKEEPER-1045:
-
{quote} Pending Work:
1. Need to support upgrade execution path. I'll update the proposal to support
this soon. {quote}
I've captured the design thoughts that comes in my mind and attached a draft
document which describes the proposal. It would be really great to see the
feedback from the community about the proposal. Thanks!
> Quorum Peer mutual authentication
> -
>
> Key: ZOOKEEPER-1045
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
>Reporter: Eugene Koontz
>Assignee: Rakesh R
> Attachments: ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade
> Design Proposal.pdf
>
>
> ZOOKEEPER-938 addresses mutual authentication between clients and servers.
> This bug, on the other hand, is for authentication among quorum peers.
> Hopefully much of the work done on SASL integration with Zookeeper for
> ZOOKEEPER-938 can be used as a foundation for this enhancement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-2266 PreCommit Build #3003
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2266 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3003/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 26 lines...] pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 10240 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Buildfile: /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml check-for-findbugs: findbugs.check: forrest.check: hudson-test-patch: [exec] [exec] [exec] == [exec] == [exec] Testing patch for ZOOKEEPER-2266. [exec] == [exec] == [exec] [exec] [exec] svn: The path '.' appears to be part of a Subversion 1.7 or greater [exec] working copy. Please upgrade your Subversion client to use this [exec] working copy. [exec] svn: The path '.' appears to be part of a Subversion 1.7 or greater [exec] working copy. Please upgrade your Subversion client to use this [exec] working copy. [exec] svn: The path '.' appears to be part of a Subversion 1.7 or greater [exec] working copy. Please upgrade your Subversion client to use this [exec] working copy. [exec] Unknown command: 'upgrade' [exec] Type 'svn help' for usage. [exec] svn: The path '.' appears to be part of a Subversion 1.7 or greater [exec] working copy. Please upgrade your Subversion client to use this [exec] working copy. BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 100 Total time: 1 second Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Publisher 'Publish JUnit test result report' failed: No test report files were found. Configuration error? Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2266 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Updated] (ZOOKEEPER-1045) Quorum Peer mutual authentication
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-1045: Attachment: ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf > Quorum Peer mutual authentication > - > > Key: ZOOKEEPER-1045 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045 > Project: ZooKeeper > Issue Type: New Feature > Components: server >Reporter: Eugene Koontz >Assignee: Rakesh R > Attachments: ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade > Design Proposal.pdf > > > ZOOKEEPER-938 addresses mutual authentication between clients and servers. > This bug, on the other hand, is for authentication among quorum peers. > Hopefully much of the work done on SASL integration with Zookeeper for > ZOOKEEPER-938 can be used as a foundation for this enhancement. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2318) segfault in auth_completion_func
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086004#comment-15086004
]
Raul Gutierrez Segales commented on ZOOKEEPER-2318:
---
[~marshall]: doesn't ring a bell... is it easy to repro with 3.4.6 or 3.5.1?
> segfault in auth_completion_func
>
>
> Key: ZOOKEEPER-2318
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2318
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
>Affects Versions: 3.5.0
>Reporter: Marshall McMullen
>
> We have seen some sporadic issues with unexplained segfaults inside
> auth_completion_func. The interesting thing is we are not using any auth
> mechanism at all. This happened against this version of the code:
> svn.apache.org/repos/asf/zookeeper/trunk@1547702
> Here's the stacktrace we are seeing:
> {code}
> Thread 1 (Thread 0x7f21d13ff700 ? (LWP 5230)):
> #0 0x7f21efff42f0 in auth_completion_func (rc=0, zh=0x7f21e7470800) at
> src/zookeeper.c:1696
> #1 0x7f21efff7898 in zookeeper_process (zh=0x7f21e7470800, events=2) at
> src/zookeeper.c:2708
> #2 0x7f21f0006583 in do_io (v=0x7f21e7470800) at src/mt_adaptor.c:440
> #3 0x7f21eeab7e9a in start_thread () from
> /lib/x86_64-linux-gnu/libpthread.so.0
> #4 0x7f21ed1803fd in clone () from /lib/x86_64-linux-gnu/libc.so.6
> #5 0x in ?? ()
> {code}
> The offending line in our case is:
> 1696LOG_INFO(LOGCALLBACK(zh), "Authentication scheme %s
> succeeded", zh->auth_h.auth->scheme);
> It must be the case that zh->auth_h.auth is NULL for this to happen since the
> code path returns if zh is NULL.
> Interesting log messages around this time:
> {code}
> Socket [10.170.243.7:2181] zk retcode=-2, errno=115(Operation now in
> progress): unexpected server response: expected 0xfff9, but received
> 0xfff8
> Priming connection to [10.170.243.4:2181]: last_zxid=0x370eb4d
> initiated connection to server [10.170.243.4:2181]
> Oct 13 12:03:21.273384 zookeeper - INFO
> [NIOServerCxnFactory.AcceptThread:/10.170.243.4:2181:NIOServerCnxnFactory$AcceptThread@296]
> - Accepted socket connection from /10.170.243.4:48523
> Oct 13 12:03:21.274321 zookeeper - WARN
> [NIOWorkerThread-24:ZooKeeperServer@822] - Connection request from old client
> /10.170.243.4:48523; will be dropped if server is in r-o mode
> Oct 13 12:03:21.274452 zookeeper - INFO
> [NIOWorkerThread-24:ZooKeeperServer@869] - Client attempting to renew session
> 0x311596d004a at /10.170.243.4:48523; client last zxid is 0x30370eb4d;
> server last zxid is 0x30370eb4d
> Oct 13 12:03:21.274584 zookeeper - INFO [NIOWorkerThread-24:Learner@115] -
> Revalidating client: 0x311596d004a
> session establishment complete on server [10.170.243.4:2181],
> sessionId=0x311596d004a, negotiated timeout=2
> Oct 13 12:03:21.275693 zookeeper - INFO
> [QuorumPeer[myid=1]/10.170.243.4:2181:ZooKeeperServer@611] - Established
> session 0x311596d004a with negotiated timeout 2 for client
> /10.170.243.4:48523
> Oct 13 12:03:24.229590 zookeeper - WARN
> [NIOWorkerThread-8:NIOServerCnxn@361] - Unable to read additional data from
> client sessionid 0x311596d004a, likely client has closed socket
> Oct 13 12:03:24.230018 zookeeper - INFO
> [NIOWorkerThread-8:NIOServerCnxn@999] - Closed socket connection for client
> /10.170.243.4:48523 which had sessionid 0x311596d004a
> Oct 13 12:03:24.230257 zookeeper - WARN
> [NIOWorkerThread-19:NIOServerCnxn@361] - Unable to read additional data from
> client sessionid 0x12743aa0001, likely client has closed socket
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-2266 PreCommit Build #3004
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2266 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3004/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 22 lines...] pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 10240 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Buildfile: /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml check-for-findbugs: findbugs.check: forrest.check: hudson-test-patch: [exec] [exec] [exec] == [exec] == [exec] Testing patch for ZOOKEEPER-2266. [exec] == [exec] == [exec] [exec] [exec] svn: The path '.' appears to be part of a Subversion 1.7 or greater [exec] working copy. Please upgrade your Subversion client to use this [exec] working copy. [exec] svn: The path '.' appears to be part of a Subversion 1.7 or greater [exec] working copy. Please upgrade your Subversion client to use this [exec] working copy. [exec] svn: The path '.' appears to be part of a Subversion 1.7 or greater [exec] working copy. Please upgrade your Subversion client to use this [exec] working copy. [exec] Unknown command: 'upgrade' [exec] Type 'svn help' for usage. [exec] svn: The path '.' appears to be part of a Subversion 1.7 or greater [exec] working copy. Please upgrade your Subversion client to use this [exec] working copy. BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1816: exec returned: 100 Total time: 0 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Recording test results Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ERROR: Publisher 'Publish JUnit test result report' failed: No test report files were found. Configuration error? Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 [description-setter] Description set: ZOOKEEPER-2266 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 Setting LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7 ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2318) segfault in auth_completion_func
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085877#comment-15085877
]
Marshall McMullen commented on ZOOKEEPER-2318:
--
Anyone else seeing this? We haven't updated our internal ZooKeeper version in
quite a while so it's possible this is fixed in newer versions
> segfault in auth_completion_func
>
>
> Key: ZOOKEEPER-2318
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2318
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
>Affects Versions: 3.5.0
>Reporter: Marshall McMullen
>
> We have seen some sporadic issues with unexplained segfaults inside
> auth_completion_func. The interesting thing is we are not using any auth
> mechanism at all. This happened against this version of the code:
> svn.apache.org/repos/asf/zookeeper/trunk@1547702
> Here's the stacktrace we are seeing:
> {code}
> Thread 1 (Thread 0x7f21d13ff700 ? (LWP 5230)):
> #0 0x7f21efff42f0 in auth_completion_func (rc=0, zh=0x7f21e7470800) at
> src/zookeeper.c:1696
> #1 0x7f21efff7898 in zookeeper_process (zh=0x7f21e7470800, events=2) at
> src/zookeeper.c:2708
> #2 0x7f21f0006583 in do_io (v=0x7f21e7470800) at src/mt_adaptor.c:440
> #3 0x7f21eeab7e9a in start_thread () from
> /lib/x86_64-linux-gnu/libpthread.so.0
> #4 0x7f21ed1803fd in clone () from /lib/x86_64-linux-gnu/libc.so.6
> #5 0x in ?? ()
> {code}
> The offending line in our case is:
> 1696LOG_INFO(LOGCALLBACK(zh), "Authentication scheme %s
> succeeded", zh->auth_h.auth->scheme);
> It must be the case that zh->auth_h.auth is NULL for this to happen since the
> code path returns if zh is NULL.
> Interesting log messages around this time:
> {code}
> Socket [10.170.243.7:2181] zk retcode=-2, errno=115(Operation now in
> progress): unexpected server response: expected 0xfff9, but received
> 0xfff8
> Priming connection to [10.170.243.4:2181]: last_zxid=0x370eb4d
> initiated connection to server [10.170.243.4:2181]
> Oct 13 12:03:21.273384 zookeeper - INFO
> [NIOServerCxnFactory.AcceptThread:/10.170.243.4:2181:NIOServerCnxnFactory$AcceptThread@296]
> - Accepted socket connection from /10.170.243.4:48523
> Oct 13 12:03:21.274321 zookeeper - WARN
> [NIOWorkerThread-24:ZooKeeperServer@822] - Connection request from old client
> /10.170.243.4:48523; will be dropped if server is in r-o mode
> Oct 13 12:03:21.274452 zookeeper - INFO
> [NIOWorkerThread-24:ZooKeeperServer@869] - Client attempting to renew session
> 0x311596d004a at /10.170.243.4:48523; client last zxid is 0x30370eb4d;
> server last zxid is 0x30370eb4d
> Oct 13 12:03:21.274584 zookeeper - INFO [NIOWorkerThread-24:Learner@115] -
> Revalidating client: 0x311596d004a
> session establishment complete on server [10.170.243.4:2181],
> sessionId=0x311596d004a, negotiated timeout=2
> Oct 13 12:03:21.275693 zookeeper - INFO
> [QuorumPeer[myid=1]/10.170.243.4:2181:ZooKeeperServer@611] - Established
> session 0x311596d004a with negotiated timeout 2 for client
> /10.170.243.4:48523
> Oct 13 12:03:24.229590 zookeeper - WARN
> [NIOWorkerThread-8:NIOServerCnxn@361] - Unable to read additional data from
> client sessionid 0x311596d004a, likely client has closed socket
> Oct 13 12:03:24.230018 zookeeper - INFO
> [NIOWorkerThread-8:NIOServerCnxn@999] - Closed socket connection for client
> /10.170.243.4:48523 which had sessionid 0x311596d004a
> Oct 13 12:03:24.230257 zookeeper - WARN
> [NIOWorkerThread-19:NIOServerCnxn@361] - Unable to read additional data from
> client sessionid 0x12743aa0001, likely client has closed socket
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2260) Paginated getChildren call
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-2260: Fix Version/s: (was: 4.0.0) 3.6.0 > Paginated getChildren call > -- > > Key: ZOOKEEPER-2260 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2260 > Project: ZooKeeper > Issue Type: New Feature >Affects Versions: 3.4.5, 3.4.6, 3.5.0, 4.0.0 >Reporter: Marco P. >Priority: Minor > Labels: api, features > Fix For: 3.6.0 > > Attachments: ZOOKEEPER-2260.patch, ZOOKEEPER-2260.patch > > > Add pagination support to the getChildren() call, allowing clients to iterate > over children N at the time. > Motivations for this include: > - Getting out of a situation where so many children were created that > listing them exceeded the network buffer sizes (making it impossible to > recover by deleting)[1] > - More efficient traversal of nodes with large number of children [2] > I do have a patch (for 3.4.6) we've been using successfully for a while, but > I suspect much more work is needed for this to be accepted. > [1] https://issues.apache.org/jira/browse/ZOOKEEPER-272 > [2] https://issues.apache.org/jira/browse/ZOOKEEPER-282 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2260) Paginated getChildren call
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086934#comment-15086934 ] Rakesh R commented on ZOOKEEPER-2260: - Good work [~mprime] I've added comments in the PR, please take a look at it. > Paginated getChildren call > -- > > Key: ZOOKEEPER-2260 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2260 > Project: ZooKeeper > Issue Type: New Feature >Affects Versions: 3.4.5, 3.4.6, 3.5.0, 4.0.0 >Reporter: Marco P. >Priority: Minor > Labels: api, features > Fix For: 3.6.0 > > Attachments: ZOOKEEPER-2260.patch, ZOOKEEPER-2260.patch > > > Add pagination support to the getChildren() call, allowing clients to iterate > over children N at the time. > Motivations for this include: > - Getting out of a situation where so many children were created that > listing them exceeded the network buffer sizes (making it impossible to > recover by deleting)[1] > - More efficient traversal of nodes with large number of children [2] > I do have a patch (for 3.4.6) we've been using successfully for a while, but > I suspect much more work is needed for this to be accepted. > [1] https://issues.apache.org/jira/browse/ZOOKEEPER-272 > [2] https://issues.apache.org/jira/browse/ZOOKEEPER-282 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2260) Paginated getChildren call
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-2260: Affects Version/s: (was: 3.4.6) (was: 3.4.5) (was: 4.0.0) > Paginated getChildren call > -- > > Key: ZOOKEEPER-2260 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2260 > Project: ZooKeeper > Issue Type: New Feature >Affects Versions: 3.4.6, 3.5.0 >Reporter: Marco P. > Labels: api, features > Fix For: 3.6.0 > > Attachments: ZOOKEEPER-2260.patch, ZOOKEEPER-2260.patch > > > Add pagination support to the getChildren() call, allowing clients to iterate > over children N at the time. > Motivations for this include: > - Getting out of a situation where so many children were created that > listing them exceeded the network buffer sizes (making it impossible to > recover by deleting)[1] > - More efficient traversal of nodes with large number of children [2] > I do have a patch (for 3.4.6) we've been using successfully for a while, but > I suspect much more work is needed for this to be accepted. > [1] https://issues.apache.org/jira/browse/ZOOKEEPER-272 > [2] https://issues.apache.org/jira/browse/ZOOKEEPER-282 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2260) Paginated getChildren call
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated ZOOKEEPER-2260: Affects Version/s: 3.4.6 > Paginated getChildren call > -- > > Key: ZOOKEEPER-2260 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2260 > Project: ZooKeeper > Issue Type: New Feature >Affects Versions: 3.4.6, 3.5.0 >Reporter: Marco P. > Labels: api, features > Fix For: 3.6.0 > > Attachments: ZOOKEEPER-2260.patch, ZOOKEEPER-2260.patch > > > Add pagination support to the getChildren() call, allowing clients to iterate > over children N at the time. > Motivations for this include: > - Getting out of a situation where so many children were created that > listing them exceeded the network buffer sizes (making it impossible to > recover by deleting)[1] > - More efficient traversal of nodes with large number of children [2] > I do have a patch (for 3.4.6) we've been using successfully for a while, but > I suspect much more work is needed for this to be accepted. > [1] https://issues.apache.org/jira/browse/ZOOKEEPER-272 > [2] https://issues.apache.org/jira/browse/ZOOKEEPER-282 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
