apache-zookeeper

问题 We have a Kafka cluster consists of 6 nodes. Five of the 6 nodes have zookeeper. A spark streaming job is reading from a streaming server, do some processing, and send the result to Kafka. From time to time the spark job got stuck, no data is sent to Kafka, and the job is restarted. The job keeps stuck and restarted until we manually restart the Kafka cluster. After restarting Kafka everything is working smoothly. Checking the Kafka logs we found this exception is thrown several times 2017-03

问题 We have a Kafka cluster consists of 6 nodes. Five of the 6 nodes have zookeeper. A spark streaming job is reading from a streaming server, do some processing, and send the result to Kafka. From time to time the spark job got stuck, no data is sent to Kafka, and the job is restarted. The job keeps stuck and restarted until we manually restart the Kafka cluster. After restarting Kafka everything is working smoothly. Checking the Kafka logs we found this exception is thrown several times 2017-03

问题 I am using Jetty 8 and ZooKeeper 3.4.5. When I connect to ZooKeeper, jetty keep generating DEBUG level message. How to suppress it? 16:54:56.757 [main-SendThread(127.0.0.1:2181)] DEBUG o.a.z.client.ZooKeeperSaslClient - Could not retrieve login configuration: java.lang.SecurityException: Unable to locate a login configuration 16:54:56.758 [main-SendThread(127.0.0.1:2181)] DEBUG o.a.z.client.ZooKeeperSaslClient - Could not retrieve login configuration: java.lang.SecurityException: Unable to

问题 I am picking up knowledge of consensus protocols in a distributed system. Such a distributed system does primary-backup on databases. I learned that "every consensus protocol can loop forever." from Leader election for paxos-based replicated key value store Where is the information source of "every consensus protocol can loop forever"? Status update: question answered. The same information source was provided by rystsov and another person of another post. Could more theoretical results and

问题 I haven't been able to find anything that directly handled the problem I'm facing, so I'm posting here. I have JUnit/JBehave tests that spin up an embedded ZooKeeper server, embedded Kafka server, and kafka producers and consumers. After upgrading kafka from 0.7 to 0.8.1.1, I'm encountering the following types of errors: ERROR [kafka-request-handler-5] state.change.logger - Error on broker 1 while processing LeaderAndIsr request correlationId 7 received from controller 1 epoch 1 for partition

问题 I'm getting the following error trying so start storm nimbus for a local dev Windows 7 workstation: Error: Could not find or load main class Files\Java\jdk1.8.0_92\bin;C:\Program storm.yaml: storm.zookeeper.servers: - "127.0.0.1" nimbus.seeds: ["127.0.0.1"] storm.local.dir: "C:\\Users\\userX\\Apps\\ApacheStorm\\apache-storm-1.0.1\\data" supervisor.slots.ports: - 6700 - 6701 - 6702 - 6703 I successfully started ZooKeeper. But when I try to run: storm nimbus from the Storm bin folder I get the

问题 I'm getting the following error trying so start storm nimbus for a local dev Windows 7 workstation: Error: Could not find or load main class Files\Java\jdk1.8.0_92\bin;C:\Program storm.yaml: storm.zookeeper.servers: - "127.0.0.1" nimbus.seeds: ["127.0.0.1"] storm.local.dir: "C:\\Users\\userX\\Apps\\ApacheStorm\\apache-storm-1.0.1\\data" supervisor.slots.ports: - 6700 - 6701 - 6702 - 6703 I successfully started ZooKeeper. But when I try to run: storm nimbus from the Storm bin folder I get the

问题 We are facing one peculiar issue with Zoo Keeper wherein the ZK loses connectivity with solr cloud all of a sudden and starts throwing an Exception which says "Cannot talk to ZooKeeper - Updates are disabled." Our application has 2 solr clusters setup separately on 2 different data centers. Each of these clusters has the same configurations and data and is expected to take the same incremental load. Application users need the changes made by them to reflect in the search with almost immediate

问题 Is there any facility in the Apache Curator lock recipes (or lower-level ZooKeeper) for auto-releasing locks that have exceeded some TTL? If not, is there a best practice for dealing with that? I see that Curator automatically releases locks in the case of the client connection being lost, which is nice...and the timeout on lock acquisition is also helpful. I'm wondering to what degree I need to protect my system by making a recurring job that looks for locks that have been around to long and

问题 I'm just getting started with Apache Kafka/Zookeeper and have been running into issues trying to set up a cluster on AWS. Currently I have three servers: One running Zookeeper and two running Kafka. I can start the Kafka servers without issue and can create topics on both of them. However, the trouble comes when I try to start a producer on one machine and a consumer on the other: on the Kafka producer: kafka-console-producer.sh --broker-list <kafka server 1 aws public dns>:9092,<kafka server