instance_id stringlengths 8 20 | system stringclasses 11
values | issue_number stringlengths 4 6 | lite bool 2
classes | title stringlengths 0 133 | description stringlengths 150 30.7k | branch stringlengths 5 40 | issue_url stringlengths 41 54 | fix_url stringlengths 39 82 ⌀ | issue_created timestamp[s]date 2016-06-09 00:00:00 2026-04-22 00:00:00 ⌀ | severity stringclasses 3
values | root_cause_type stringclasses 7
values | bug_complexity stringclasses 5
values | distributed bool 2
classes | contains_analysis bool 2
classes | analysis_removed stringclasses 3
values | contains_logs bool 2
classes | contains_stack_traces bool 2
classes | num_artifacts int64 0 9 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
tikv-19220 | tikv | 19220 | false | load base split can not work when scan table | Bug Report
What did you do?
1、create a small table
2、run oltp_write_only
3、table full scan
What did you expect to see?
region can be splited
What did you see instead?
region can not be splited
What version of PD are you using (pd-server -V)?
./pd-server -V
Release Version: v9.0.0-beta.2.pre-223-gaef91a5
Edition: Com... | aef91a5ee6d6747b611f78f3874babd06af2d67d | https://github.com/tikv/tikv/issues/19220 | https://github.com/tikv/tikv/pull/19223 | 2025-12-18T00:00:00 | Major | Logic | Easy | false | false | N/A | false | false | 0 |
tikv-19238 | tikv | 19238 | false | Log Backup may get stuck due to async lock held across .await | Bug Report
Under certain configurations, Log Backup may get permanently stuck.
Once this happens:
Log backup no longer makes progress, no related backup log output
Pause/Stop task commands do not work
This issue is strongly correlated with holding an async lock across .await, which may stall the Tokio runtime when th... | v8.5.3 | https://github.com/tikv/tikv/issues/19238 | https://github.com/tikv/tikv/pull/19252 | 2025-12-26T00:00:00 | Major | Concurrency | Medium | false | true | No | false | false | 0 |
zookeeper-2581 | zookeeper | 2581 | true | Not handled NullPointerException while creating key manager and trustManager | Not handled NullPointerException while creating key manager and trustManager:-
2016-09-14 13:35:23,488 [myid:1] - ERROR [CommitProcWorkThread-1:X509AuthenticationProvider@78] - Failed to create key manager
org.apache.zookeeper.common.X509Exception$KeyManagerException: java.lang.NullPointerException
at org.apache.zooke... | release-3.5.1 | https://issues.apache.org/jira/browse/ZOOKEEPER-2581 | https://github.com/apache/zookeeper/commit/88c1c93 | 2016-09-14T00:00:00 | Major | Error handling | Medium | false | false | N/A | true | true | 0 |
zookeeper-2623 | zookeeper | 2623 | false | CheckVersion outside of Multi causes NullPointerException | I wasn't sure if check version (opcode 13) was permitted outside of a multi op, so I tried it. My server crashed with a NullPointerException and became unusable until restarted. I guess it's not allowed, but perhaps the server should handle this more gracefully?
Here are the server logs:
Accepted socket connection fr... | release-3.9.0 | https://issues.apache.org/jira/browse/ZOOKEEPER-2623 | https://github.com/apache/zookeeper/pull/1988 | 2016-10-28T00:00:00 | Critical | Error handling | Hard | false | false | N/A | true | true | 0 |
zookeeper-2775 | zookeeper | 2775 | false | ZK Client not able to connect with Xid out of order error | During Network unreachable scenario in one of the cluster, we observed Xid out of order and Nothing in the queue error continously. And ZK client it finally not able to connect successully to ZK server.
Logs:
unexpected error, closing socket connection and attempting reconnect | org.apache.zookeeper.ClientCnxn (Clien... | release-3.5.3 | https://issues.apache.org/jira/browse/ZOOKEEPER-2775 | https://github.com/apache/zookeeper/commit/0026e27 | 2017-05-05T00:00:00 | Critical | Logic | Easy | true | true | No | true | true | 0 |
zookeeper-2836 | zookeeper | 2836 | false | QuorumCnxManager.Listener Thread Better handling of SocketTimeoutException | QuorumCnxManager Listener thread blocks SocketServer on accept but we are getting SocketTimeoutException on our boxes after 49days 17 hours . As per current code there is a 3 times retry and after that it says "As I'm leaving the listener thread, I won't be able to participate in leader election any longer: $<hostname>... | release-3.5.3 | https://issues.apache.org/jira/browse/ZOOKEEPER-2836 | https://github.com/apache/zookeeper/pull/336 | 2017-07-04T00:00:00 | Critical | Error handling | Medium | true | false | N/A | false | false | 0 |
zookeeper-2845 | zookeeper | 2845 | true | Data inconsistency issue due to retain database in leader election | In ZOOKEEPER-2678, the ZKDatabase is retained to reduce the unavailable time during leader election. In ZooKeeper ensemble, it's possible that the snapshot is ahead of txn file (due to slow disk on the server, etc), or the txn file is ahead of snapshot due to no commit message being received yet.
If snapshot is ahead ... | release-3.5.3 | https://issues.apache.org/jira/browse/ZOOKEEPER-2845 | https://github.com/apache/zookeeper/commit/ffb81b9 | 2017-07-14T00:00:00 | Critical | Concurrency | Hard | true | true | No | false | false | 0 |
zookeeper-2959 | zookeeper | 2959 | false | ignore accepted epoch and LEADERINFO ack from observers when a newly elected leader computes new epoch | Once the ZooKeeper cluster finishes the election for new leader, all learners report their accepted epoch to the leader for the computation of new cluster epoch.
The computation will get an outcome once :
- The leader has call method "getEpochToPropose"
- The number of all reporters is greater than half of participan... | release-3.5.3 | https://issues.apache.org/jira/browse/ZOOKEEPER-2959 | https://github.com/apache/zookeeper/commit/088dfdf | 2017-12-20T00:00:00 | Blocker | Logic | Easy | true | true | Partly Removed | false | false | 0 |
zookeeper-2960 | zookeeper | 2960 | false | The dataDir and dataLogDir are used opposingly | _emphasized text_After upgrading from zookeeper 3.4.5, to 3.4.11, without editing zoo.cfg, the new version of the server tries to use the dataDir as the dataLogDir, and the dataLogDir as the dataDir. Or at least some parts of the server.
Configuration file has:
$ grep -i data /etc/zookeeper/zoo.cfg
dataLogDir=/var/l... | release-3.4.11 | https://issues.apache.org/jira/browse/ZOOKEEPER-2960 | https://github.com/apache/zookeeper/pull/441 | 2017-12-22T00:00:00 | Critical | Logic | Hard | false | false | N/A | true | false | 0 |
zookeeper-2982 | zookeeper | 2982 | true | Re-try DNS hostname -> IP resolution | ZOOKEEPER-1506 fixed a DNS resolution issue in 3.4. Some portions of the fix haven't yet been ported to 3.5.
To recap the outstanding problem in 3.5, if a given ZK server is started before all peer addresses are resolvable, that server may cache a negative lookup result and forever fail to resolve the address. For exa... | release-3.5.3 | https://issues.apache.org/jira/browse/ZOOKEEPER-2982 | https://github.com/apache/zookeeper/pull/513 | 2018-02-19T00:00:00 | Blocker | Error handling | Hard | true | false | N/A | true | true | 0 |
zookeeper-3218 | zookeeper | 3218 | false | zk server reopened，the interval for observer connect to the new leader is too long，then session expired | two participants、one observer，zkclient connect to observer。
Then，close the two participants，the zookeeper server cloesed
Ten seconds later，reopen the two participants，and leader selected
----------------------------------------------------------------------------
But the observer can't connect to the new leader imm... | release-3.5.5 | https://issues.apache.org/jira/browse/ZOOKEEPER-3218 | https://github.com/apache/zookeeper/pull/747 | 2018-12-17T00:00:00 | Major | Logic | Medium | true | true | No | false | false | 0 |
zookeeper-3642 | zookeeper | 3642 | false | Data inconsistency when the leader crashes right after sending SNAP sync | If the leader crashes after sending a SNAP sync to a learner, but before sending the NEWLEADER message, the learner will not save the snapshot to disk. But it will advance its lastProcessedZxid to that from the snapshot (call it Zxid X)
A new leader will get elected, and it will resync our learner again immediately. B... | release-3.5.6 | https://issues.apache.org/jira/browse/ZOOKEEPER-3642 | https://github.com/apache/zookeeper/commit/161e505 | 2019-12-09T00:00:00 | Major | Concurrency | Hard | true | true | Partly Removed | false | false | 0 |
zookeeper-3644 | zookeeper | 3644 | false | Data loss after upgrading standalone ZK server 3.4.14 to 3.5.6 with snapshot.trust.empty=true | We have tried to upgrade single node standalone ZK server from 3.4.14 to 3.5.6. There were no snapshot files, so as suggested in ZOOKEEPER-3056, we have set snapshot.trust.empty to true. After server startup, when we tried to list the znodes, we found that znodes are missing.
Steps to reproduce:
Start a single node ... | release-3.5.6 | https://issues.apache.org/jira/browse/ZOOKEEPER-3644 | https://github.com/apache/zookeeper/commit/a314855 | 2019-12-10T00:00:00 | Blocker | Logic | Hard | false | true | No | true | false | 0 |
zookeeper-3656 | zookeeper | 3656 | false | SyncRequestProcessor doesn't update lastFlushTime correctly on observers | This issues was introduced in ZOOKEEPER-3311. The lastFlushTime used to decide the batch window is not updated correctly for the observer case when the nextProcessor is always be null.
This can cause observers to fall behind and their sync queue to grow indefinitely. | release-3.6.3 | https://issues.apache.org/jira/browse/ZOOKEEPER-3656 | https://github.com/apache/zookeeper/pull/1189 | 2019-12-19T00:00:00 | Major | Logic | Easy | false | false | N/A | false | false | 0 |
zookeeper-3769 | zookeeper | 3769 | false | fast leader election does not end if leader is taken down | In a cluster with three nodes, node3 is the leader and the other nodes are followers.
If I stop node3, the other two nodes do not finish the leader election.
This is happening with ZK 3.5.7, openjdk version "12.0.2" 2019-07-16, and this config
tickTime=2000
initLimit=30
syncLimit=3
dataDir=/company/service/data
... | release-3.5.7 | https://issues.apache.org/jira/browse/ZOOKEEPER-3769 | https://github.com/apache/zookeeper/commit/68466c8 | 2020-03-24T00:00:00 | Major | Error handling | Medium | true | false | N/A | true | false | 3 |
zookeeper-3829 | zookeeper | 3829 | false | Zookeeper refuses request after node expansion | It's easy to reproduce this bug.
//代码占位符
Step 1. Deploy 3 nodes A,B,C with configuration A,B,C .
Step 2. Deploy node ` D` with configuration `A,B,C,D` , cluster state is ok now.
Step 3. Restart nodes A,B,C with configuration A,B,C,D, then the leader will be D, cluster hangs, but it can accept `mntr` command, other... | release-3.6.1 | https://issues.apache.org/jira/browse/ZOOKEEPER-3829 | https://github.com/apache/zookeeper/commit/48f037f | 2020-05-15T00:00:00 | Major | Logic | Hard | true | true | No | false | false | 2 |
zookeeper-3988 | zookeeper | 3988 | false | org.apache.zookeeper.server.NettyServerCnxn.receiveMessage throws NullPointerException | While upgrading K8S cluster, container running zookeeper will rollover one by one.
During this rollover, Null Pointer Exception was observed as below.
INFO [QuorumPeer[myid=1](plain=0.0.0.0:2181)(secure=0.0.0.0:2281):Follower@292] - shutdown FollowerINFO [QuorumPeer[myid=1](plain=0.0.0.0:2181)(secure=0.0.0.0:2281):F... | release-3.7.0 | https://issues.apache.org/jira/browse/ZOOKEEPER-3988 | https://github.com/apache/zookeeper/commit/56f807f | 2020-11-02T00:00:00 | Major | Error handling | Medium | false | false | N/A | true | true | 0 |
zookeeper-4699 | zookeeper | 4699 | false | zh->hostname heap-use-after-free in zookeeper_interest | we got an asan error. The usage is one separate thread call zoo_set_servers periodically. It will use lock to make (free and reset zh->hostname operation) atomic:
// NOTE: guard access to{hostname, addr_cur, addrs, addrs_old, addrs_new}lock_reconfig(zh);
in the mean while the io thread will call zoo_interest function ... | release-3.8.1 | https://issues.apache.org/jira/browse/ZOOKEEPER-4699 | https://github.com/apache/zookeeper/pull/2138 | 2023-05-24T00:00:00 | Blocker | Concurrency | Easy | true | true | No | false | false | 0 |
zookeeper-4761 | zookeeper | 4761 | false | Cli tool read saved clientid fail | A very simple bug when reading saved clientid using fread. It causes the cli tool fail to recover from the last session connected to zookeeper server. | release-3.7.0 | https://issues.apache.org/jira/browse/ZOOKEEPER-4761 | https://github.com/apache/zookeeper/pull/2079 | 2023-10-16T00:00:00 | Major | Logic | Medium | false | false | N/A | false | false | 0 |
zookeeper-4921 | zookeeper | 4921 | false | Zookeeper Client 3.9.3 Fails to Reconnect After Network Failures | After upgrading the Java Zookeeper client to version 3.9.3, we observed that it is not resilient to brief network disruptions, such as a short VPN blip. In such cases, the client attempts to reconnect only once, and if unsuccessful, the session expires.
Apr 23, 2025 10:19:23 AM com.twitter.finagle.common.zookeeper.Zoo... | release-3.9.3 | https://issues.apache.org/jira/browse/ZOOKEEPER-4921 | https://github.com/apache/zookeeper/pull/2252 | 2025-04-23T00:00:00 | Critical | Error handling | Easy | true | false | N/A | true | true | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.