[jira] [Commented] (ZOOKEEPER-2033) zookeeper follower fails to start after a restart immediately following a new epoch
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728269#comment-14728269 ] Flavio Junqueira commented on ZOOKEEPER-2033: - I believe the real issue is that proposals should have be empty in this case and it isn't. It seems that the leader is populating committedLog and generating a snapshot by the end of the synchronization phase, but it is not updating the committedLog list accordingly. I don't know if [~asadpanda] is still interested in finishing this up after such a long time, but I can give it a shot otherwise. > zookeeper follower fails to start after a restart immediately following a new > epoch > --- > > Key: ZOOKEEPER-2033 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2033 > Project: ZooKeeper > Issue Type: Bug > Components: quorum >Affects Versions: 3.4.6 >Reporter: Asad Saeed >Assignee: Asad Saeed > Fix For: 3.4.7 > > Attachments: ZOOKEEPER-2033-3.4.patch, ZOOKEEPER-2033.patch > > > The following issue was seen when adding a new node to a zookeeper cluster. > Reproduction steps > 1. Create a 2 node ensemble. Write some keys. > 2. Add another node to the ensemble, by modifying the config. Restarting > entire cluster. > 3. Restart the new node before writing any new keys. > What occurs is that the new node gets a SNAP from the newly elected leader, > since it is too far behind. The zxid for this snapshot is from the new epoch > but that is not in the committed log cache. > On restart of this new node. The follower sends the new epoch zxid. The > leader looks at it's maxCommitted logs, and sees that it is not the newest > epoch, and therefore sends a TRUNC. > The follower sees the TRUNC but it only has a snapshot, so it cannot truncate! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[ANNOUNCE] Apache ZooKeeper 3.5.1-alpha
The Apache ZooKeeper team is proud to announce Apache ZooKeeper version 3.5.1-alpha. ZooKeeper is a high-performance coordination service for distributed applications. It exposes common services - such as naming, configuration management, synchronization, and group services - in a simple interface so you don't have to write them from scratch. You can use it off-the-shelf to implement consensus, group management, leader election, and presence protocols. And you can build on it for your own, specific needs. This is an alpha quality release that contains many bug fixes and improvements. It also introduces a few new features, including container znodes and SSL support for client-server communication. For ZooKeeper release details and downloads, visit: http://zookeeper.apache.org/releases.html ZooKeeper 3.5.1-alpha Release Notes are at: http://zookeeper.apache.org/doc/r3.5.1-alpha/releasenotes.html We would like to thank the contributors that made the release possible. Regards, The ZooKeeper Team
[jira] [Commented] (ZOOKEEPER-2238) Support limiting the maximum number of connections/clients to a zookeeper server.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728513#comment-14728513 ] nijel commented on ZOOKEEPER-2238: -- [~eribeiro] Thanks for taking up the issue. Please let me know whether you started the work. > Support limiting the maximum number of connections/clients to a zookeeper > server. > - > > Key: ZOOKEEPER-2238 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2238 > Project: ZooKeeper > Issue Type: Improvement >Reporter: nijel >Assignee: Edward Ribeiro > > Currently zookeeper have the feature of limiting the maximum number of > connection/client per IP or Host (maxClientCnxns). > But to safe guard zookeeper server from DoS attack due to many clients from > different IPs, it is better to have a limit of total number of > connections/clients to a a single member of the ZooKeeper ensemble as well. > So the idea is to introduce a new configuration to limit the maximum number > of total connections/clients. > Please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2263) ZooKeeper server should not start when neither clientPort no secureClientPort is configured
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michi Mutsuzaki updated ZOOKEEPER-2263: --- Fix Version/s: (was: 3.5.1) 3.6.0 3.5.2 > ZooKeeper server should not start when neither clientPort no secureClientPort > is configured > --- > > Key: ZOOKEEPER-2263 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2263 > Project: ZooKeeper > Issue Type: Bug >Reporter: Arshad Mohammad >Assignee: Arshad Mohammad >Priority: Minor > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2263-01.patch, ZOOKEEPER-2263-02.patch > > > ZooKeeper server should not start when neither clientPort no secureClientPort > is configured. > Without any client port ZooKeeper server can not server any purpose. It > should simply return with proper error message -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2261) When only secureClientPort is configured connections, configuration, connection_stat_reset, and stats admin commands throw NullPointerException
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michi Mutsuzaki updated ZOOKEEPER-2261:
---
Fix Version/s: (was: 3.5.1)
3.6.0
3.5.2
> When only secureClientPort is configured connections, configuration,
> connection_stat_reset, and stats admin commands throw NullPointerException
> ---
>
> Key: ZOOKEEPER-2261
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2261
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
> Fix For: 3.5.2, 3.6.0
>
>
> When only secureClientPort is configured connections, configuration,
> connection_stat_reset and stats admin commands throw NullPointerException.
> Here is stack trace one of the connections command.
> {code}
> java.lang.NullPointerException
> at
> org.apache.zookeeper.server.admin.Commands$ConsCommand.run(Commands.java:177)
> at
> org.apache.zookeeper.server.admin.Commands.runCommand(Commands.java:92)
> at
> org.apache.zookeeper.server.admin.JettyAdminServer$CommandServlet.doGet(JettyAdminServer.java:166)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2252) Random test case failure in org.apache.zookeeper.test.StaticHostProviderTest
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michi Mutsuzaki updated ZOOKEEPER-2252:
---
Fix Version/s: (was: 3.5.1)
3.5.2
> Random test case failure in org.apache.zookeeper.test.StaticHostProviderTest
>
>
> Key: ZOOKEEPER-2252
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2252
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Arshad Mohammad
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZK-2252-try-repro-on-jenkins.patch,
> ZOOKEEPER-2252-02.patch, ZOOKEEPER-2252-03.patch, ZOOKEEPER-2252-04.patch
>
>
> Test
> {{org.apache.zookeeper.test.StaticHostProviderTest.testTwoInvalidHostAddresses()}}
> fails randomly.
> Refer bellow test ci buils:
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2827/testReport/
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2828/testReport/
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2830/testReport/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
