{"instance_id": "elasticsearch-59649", "system": "elasticsearch", "issue_number": "59649", "lite": false, "title": "Dedicated voting-only master-eligible node requires access to snapshot repositories for verification", "description": "Today a snapshot repository verification ensures that all master-eligible and data nodes have write access to the snapshot repository (and can see each other's data) since taking a snapshot requires data nodes and the currently-elected master to write to the repository. However, a dedicated voting-only master-eligible node is not a data node and will never be the elected master so we should not require it to have write access to the repository.\n", "branch": "24143b07a47339e9455b5b2d0b20b5f6a352134e", "issue_url": "https://github.com/elastic/elasticsearch/issues/59649", "fix_url": "https://github.com/elastic/elasticsearch/pull/61016", "issue_created": "2020-07-15", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-85839", "system": "elasticsearch", "issue_number": "85839", "lite": false, "title": "RecoverySourceHandler#runWithGenericThreadPool caused deadlock", "description": "We saw a benchmark of a 7.17.2 cluster get stuck with all generic threads blocked in RecoverySourceHandler#runWithGenericThreadPool (see many-shards-threaddump.txt.gz):\n\n$ python ~/src/jstack2json/jstack2json.py many-shards-threaddump.txt | jq '.[].threads[] | select(.elasticsearch.threadpool == \"generic\")' -cMr | wc -l\n 144\n$ python ~/src/jstack2json/jstack2json.py many-shards-threaddump.txt | jq '.[].threads[] | select(.elasticsearch.threadpool == \"generic\") | .stack' -cMr | sed -e 's/parking to wait for <0x[0-9a-f]*>//' | sort -u | wc -l\n 1\n$ python ~/src/jstack2json/jstack2json.py many-shards-threaddump.txt | jq '.[].threads[] | select(.elasticsearch.threadpool == \"generic\") | .stack' -cMr | head -n1 | jq '.[]' -cMr\nat jdk.internal.misc.Unsafe.park(java.base@17.0.2/Native Method)\n- parking to wait for <0x0000000496000040> (a org.elasticsearch.common.util.concurrent.BaseFuture$Sync)\nat java.util.concurrent.locks.LockSupport.park(java.base@17.0.2/LockSupport.java:211)\nat java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@17.0.2/AbstractQueuedSynchronizer.java:715)\nat java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(java.base@17.0.2/AbstractQueuedSynchronizer.java:1047)\nat org.elasticsearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:243)\nat org.elasticsearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:75)\nat org.elasticsearch.common.util.concurrent.FutureUtils.get(FutureUtils.java:45)\nat org.elasticsearch.indices.recovery.RecoverySourceHandler.runWithGenericThreadPool(RecoverySourceHandler.java:486)\nat org.elasticsearch.indices.recovery.RecoverySourceHandler.lambda$acquireSafeCommit$21(RecoverySourceHandler.java:476)\nat org.elasticsearch.indices.recovery.RecoverySourceHandler$$Lambda$6704/0x0000000801a21000.run(Unknown Source)\nat org.elasticsearch.index.engine.Engine$IndexCommitRef.close(Engine.java:1919)\nat org.elasticsearch.core.internal.io.IOUtils.close(IOUtils.java:74)\nat org.elasticsearch.core.internal.io.IOUtils.close(IOUtils.java:116)\nat org.elasticsearch.core.internal.io.IOUtils.close(IOUtils.java:66)\nat org.elasticsearch.indices.recovery.RecoverySourceHandler.lambda$recoverToTarget$7(RecoverySourceHandler.java:283)\nat org.elasticsearch.indices.recovery.RecoverySourceHandler$$Lambda$6706/0x0000000801a21480.accept(Unknown Source)\nat org.elasticsearch.action.ActionListener$1.onResponse(ActionListener.java:136)\nat org.elasticsearch.common.util.concurrent.ListenableFuture.notifyListenerDirectly(ListenableFuture.java:113)\nat org.elasticsearch.common.util.concurrent.ListenableFuture.done(ListenableFuture.java:100)\nat org.elasticsearch.common.util.concurrent.BaseFuture.set(BaseFuture.java:131)\nat org.elasticsearch.common.util.concurrent.ListenableFuture.onResponse(ListenableFuture.java:139)\nat org.elasticsearch.action.StepListener.innerOnResponse(StepListener.java:52)\nat org.elasticsearch.action.NotifyOnceListener.onResponse(NotifyOnceListener.java:29)\nat org.elasticsearch.indices.recovery.RecoverySourceHandler.lambda$recoverFilesFromSourceAndSnapshot$32(RecoverySourceHandler.java:762)\nat org.elasticsearch.indices.recovery.RecoverySourceHandler$$Lambda$6735/0x0000000801890000.accept(Unknown Source)\nat org.elasticsearch.action.ActionListener$1.onResponse(ActionListener.java:136)\nat org.elasticsearch.common.util.concurrent.ListenableFuture.notifyListenerDirectly(ListenableFuture.java:113)\nat org.elasticsearch.common.util.concurrent.ListenableFuture.done(ListenableFuture.java:100)\nat org.elasticsearch.common.util.concurrent.BaseFuture.set(BaseFuture.java:131)\nat org.elasticsearch.common.util.concurrent.ListenableFuture.onResponse(ListenableFuture.java:139)\nat org.elasticsearch.action.StepListener.innerOnResponse(StepListener.java:52)\nat org.elasticsearch.action.NotifyOnceListener.onResponse(NotifyOnceListener.java:29)\nat org.elasticsearch.action.ActionListener$MappedActionListener.onResponse(ActionListener.java:101)\nat org.elasticsearch.action.ActionListener$DelegatingActionListener.onResponse(ActionListener.java:186)\nat org.elasticsearch.action.ActionListener$MappedActionListener.onResponse(ActionListener.java:101)\nat org.elasticsearch.action.ActionListener$RunBeforeActionListener.onResponse(ActionListener.java:389)\nat org.elasticsearch.action.support.RetryableAction$RetryingListener.onResponse(RetryableAction.java:143)\nat org.elasticsearch.action.ActionListener$RunBeforeActionListener.onResponse(ActionListener.java:389)\nat org.elasticsearch.action.ActionListenerResponseHandler.handleResponse(ActionListenerResponseHandler.java:43)\nat org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleResponse(TransportService.java:1471)\nat org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleResponse(TransportService.java:1471)\nat org.elasticsearch.transport.InboundHandler.doHandleResponse(InboundHandler.java:340)\nat org.elasticsearch.transport.InboundHandler.lambda$handleResponse$1(InboundHandler.java:328)\nat org.elasticsearch.transport.InboundHandler$$Lambda$5302/0x000000080188aa90.run(Unknown Source)\nat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:718)\nat java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.2/ThreadPoolExecutor.java:1136)\nat java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.2/ThreadPoolExecutor.java:635)\nat java.lang.Thread.run(java.base@17.0.2/Thread.java:833)\nDo we really need to block in this method, or can these actions just be fire-and-forget things? I couldn't see an obvious reason for needing to wait for them to complete.\n\n(FWIW this was clearly caused by setting cluster.routing.allocation.node_concurrent_recoveries too high, but really we shouldn't deadlock in any configuration)", "branch": "44fa734bbd60a571dfa49d8e80440df9fc85e105", "issue_url": "https://github.com/elastic/elasticsearch/issues/85839", "fix_url": "https://github.com/elastic/elasticsearch/pull/86127", "issue_created": "2022-04-12", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "elasticsearch-87237", "system": "elasticsearch", "issue_number": "87237", "lite": false, "title": "StoreRecovery#restore may invoke Repository#restoreShard on transport thread", "description": "This code involves getRepositoryData which may complete its listener on a transport worker:\nelasticsearch/server/src/main/java/org/elasticsearch/index/shard/StoreRecovery.java\nLines 528 to 547 in 898d849\n\n final StepListener indexIdListener = new StepListener<>(); \n // If the index UUID was not found in the recovery source we will have to load RepositoryData and resolve it by index name \n if (indexId.getId().equals(IndexMetadata.INDEX_UUID_NA_VALUE)) { \n // BwC path, running against an old version master that did not add the IndexId to the recovery source \n repository.getRepositoryData(indexIdListener.map(repositoryData -> repositoryData.resolveIndexId(indexId.getName()))); \n } else { \n indexIdListener.onResponse(indexId); \n } \n assert indexShard.getEngineOrNull() == null; \n indexIdListener.whenComplete( \n idx -> repository.restoreShard( \n indexShard.store(), \n restoreSource.snapshot().getSnapshotId(), \n idx, \n snapshotShardId, \n indexShard.recoveryState(), \n restoreListener \n ), \n restoreListener::onFailure \n ); \nHowever the listener in question calls Repository#restoreShard which involves blocking calls and should not run on a transport worker.\n\n", "branch": "35b48729b183bc180914146a361609f01b08b921", "issue_url": "https://github.com/elastic/elasticsearch/issues/87237", "fix_url": "https://github.com/elastic/elasticsearch/pull/87264", "issue_created": "2022-05-31", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-90442", "system": "elasticsearch", "issue_number": "90442", "lite": false, "title": "Disk indicator - Cover edge case where data node is out of space but has no indices.", "description": "Current behaviour\nThe disk indicator reports the following when a data node is yellow or red but has no indices.\n\nSymptom:\n1 node with roles: [data] is out of disk or running low on disk space.\n\nImpact: None\nDiagnosis: 0 indices reside on nodes that have run or are likely to run out of space, this can temporarily disable writing on these indices. Enable autoscaling (if applicable), add disk capacity or free up disk space to resolve this. If you have already taken action please wait for the rebalancing to complete.\n\nExpected behaviour\nThe disk indicator reports the following when a data node is yellow or red but has no indices.\n\nSymptom:\n1 node with roles: [data] is out of disk or running low on disk space.\n\nImpact:\n1 node with roles: [data] has run out or is likely to run out of disk space, this node cannot be used by the cluster to store data. AREA: DEPLOYMENT_MANAGEMENT\n\nDiagnosis:\nDisk is almost full. Enable autoscaling (if applicable), add disk capacity or free up disk space to resolve this. If you have already taken action please wait for the rebalancing to complete.\n\nAs an area of impact I added DEPLOYMENT_MANAGEMENT considering that this is not a healthy deployment if one node is not usable. I am trying to avoid listing INGEST since for now we can still ingest data. Any thoughts?\n\nSee: #90305\n", "branch": "9e6a784aa57877fcfe0352862356d4866aabb3ab", "issue_url": "https://github.com/elastic/elasticsearch/issues/90442", "fix_url": "https://github.com/elastic/elasticsearch/pull/90772", "issue_created": "2022-09-28", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": false, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-93542", "system": "elasticsearch", "issue_number": "93542", "lite": false, "title": "Peer recovery may time out during recoverLocallyUpToGlobalCheckpoint", "description": "The recoverLocallyUpToGlobalCheckpoint step of peer recovery may take an extended period of time, but today we do not disable the recovery monitor during this step so if it takes more than 30 minutes (by default) then the recovery will time out, fail, and retry repeatedly. We should disable the recovery monitor during this step.\n\n", "branch": "052a4f15b92713e422560ddee70050744f94555a", "issue_url": "https://github.com/elastic/elasticsearch/issues/93542", "fix_url": "https://github.com/elastic/elasticsearch/pull/93551", "issue_created": "2023-02-07", "severity": "Major", "root_cause_type": "Performance", "bug_complexity": "Hard", "distributed": false, "contains_analysis": false, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-96544", "system": "elasticsearch", "issue_number": "96544", "lite": false, "title": "Cluster health computation sometimes runs on applier thread", "description": "In #90621 we moved most usages of the cluster health API onto a MANAGEMENT thread because it's too expensive to run on SAME in a large cluster. However, if the request includes any wait_for_* option then we set up a cluster state observer, which supplies its responses on the cluster applier thread. We need to fork those computations onto a MANAGEMENT thread too.\n\n", "branch": "6caf9c1f60ba0b993dbb3d6cf97768275e9975fc", "issue_url": "https://github.com/elastic/elasticsearch/issues/96544", "fix_url": "https://github.com/elastic/elasticsearch/pull/98904", "issue_created": "2023-06-03", "severity": "Critical", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-98926", "system": "elasticsearch", "issue_number": "98926", "lite": false, "title": "Health API reports disk information Unknown status / No disk usage data symptom", "description": "Elasticsearch Service (ESS) users have observed the below error message when accessing the Health API of a deployment:\\n\\nError: Cannot read properties of undefined (reading 'replace\\\")\\nat https://cloud.elastic.co/app.070493148d8f8558ab6.js:2:3103121\\nat U1 (https://cloud.elastic.co/app.070493148d88558ab6.js:2:3103141) \\nat a (https://cloud.elastic.co/vendor.3ccc0c4579678245a4e.js:2:5829841) \\nat $ (https://cloud.elastic.co/vendor.3ccc0c4579678245a4e.js:2:5881966) \\nat Tl (https: //cloud.elastic.co/vendor.3ccc@c4579678245a4e. js:2:5869244) \\nat El (https: //cloud.elastic.co/vendor.3ccc@c4579678245a4e.j:2:5869172) \\nat _1 (https://cloud.elastic.co/vendor.3ccc0c4579678245a4e.js:2:5869035) \\nat yl (https: //cloud.elastic.co/vendor.3ccc@c4579678245a4e. js:2:5866022)\\nat https://cloud.elastic.co/vendor.3ccc0c4579678245a4e.js:2:5815760\\nat t.unstable_runWithPriority (https://cloud.elastic.co/vendor.3ccc@c457967e8245a4e. js:2:6649725)\\nat Go (https: //cloud.elastic.co/vendor.3ccc@c457967e8245a4e. js:2:5815537) \\nat Xo (https: //cloud.elastic.co/vendor.3ccc@c4579678245a4e. js:2:5815705) \\nat $o (https: //cloud.elastic.co/vendor.3ccc0c457967e8245a4e.js:2:5815640) \\nat Ml (https: //cloud.elastic.co/vendor. 3ccc0c4579678245a4e. js:2:5866343)\\nat Object.notify (https: //cloud.elastic.co/vendor.3ccc@c457967e8245a4e. js:2:5977078)\\nat Object.notifyNestedSubs (https://cloud.elastic.co/vendor.3ccc@c457967e8245a4e. js:2:5977491)\\nFurther investigation revealed that the Cloud UI is unable to gracefully handle the following disk information returned by the Health API\\n\\n \\\"disk\\\" : {\\n \\\"status\\\" : \\\"Unknown\\\",\\n \\\"symptom\\\" : \\\"No disk usage data.\\\"\\n },\\nWhile the above error can be better handled in ESS, it is unclear why the Health API reports such disk status / symptom. This requires further investigation.\\n\\nWorkaround\\nUsers can disable and enable again the health node in Elasticsearch. These are the required APIs:\\n\\nDisable health node:\\nPUT _cluster/settings\\n{\\n \\\"persistent\\\": {\\n \\\"health.node.enabled\\\": false\\n }\\n}\\nEnable health node:\\nPUT _cluster/settings\\n{\\n \\\"persistent\\\": {\\n \\\"health.node.enabled\\\": true\\n }\\n}\\nOnce the two APIs are executed, observe that the Health page is accessible again.\\n\\nSteps to Reproduce\\nIn ESS, create a deployment:\\n2GB RAM x 2AZ (hot tier)\\nVersion 7.17.6\\nWait for the deployment to be created, take a snapshot:\\nPOST _slm/policy/cloud-snapshot-policy/_execute\\nCreate another deployment:\\nSame topology (same region, 2GB RAM x 2AZ (hot tier))\\nVersion 8.9.1\\nRestore snapshot from the 7.17.6 deployment (by toggling the Restore snapshot data when creating the deployment)\\nWait for the deployment version 8.9.1 to be created, access the Health page and observe the above error message.\\nRun the Health API:\\n{\\n \\\"status\\\": \\\"unknown\\\",\\n \\\"cluster_name\\\": \\\"xxx\\\",\\n \\\"indicators\\\": {\\n \\\"master_is_stable\\\": {\\n \\\"status\\\": \\\"green\\\",\\n \\\"symptom\\\": \\\"The cluster has a stable master node\\\",\\n \\\"details\\\": {\\n \\\"current_master\\\": {\\n \\\"node_id\\\": \\\"4XoNLHsXR3aiO4kqb_x__g\\\",\\n \\\"name\\\": \\\"instance-0000000001\\\"\\n },\\n \\\"recent_masters\\\": [\\n {\\n \\\"node_id\\\": \\\"YE16I4OrQP60r0A9hGYMhg\\\",\\n \\\"name\\\": \\\"instance-0000000000\\\"\\n },\\n {\\n \\\"node_id\\\": \\\"4XoNLHsXR3aiO4kqb_x__g\\\",\\n \\\"name\\\": \\\"instance-0000000001\\\"\\n }\\n ]\\n }\\n },\\n \\\"repository_integrity\\\": {\\n \\\"status\\\": \\\"green\\\",\\n \\\"symptom\\\": \\\"No corrupted snapshot repositories.\\\",\\n \\\"details\\\": {\\n \\\"total_repositories\\\": 2\\n }\\n },\\n \\\"shards_availability\\\": {\\n \\\"status\\\": \\\"green\\\",\\n \\\"symptom\\\": \\\"This cluster has all shards available.\\\",\\n \\\"details\\\": {\\n \\\"started_primaries\\\": 27,\\n \\\"unassigned_primaries\\\": 0,\\n \\\"initializing_replicas\\\": 0,\\n \\\"started_replicas\\\": 27,\\n \\\"initializing_primaries\\\": 0,\\n \\\"restarting_replicas\\\": 0,\\n \\\"restarting_primaries\\\": 0,\\n \\\"unassigned_replicas\\\": 0,\\n \\\"creating_primaries\\\": 0\\n }\\n },\\n \\\"disk\\\": {\\n \\\"status\\\": \\\"unknown\\\",\\n \\\"symptom\\\": \\\"No disk usage data.\\\"\\n },\\n \\\"shards_capacity\\\": {\\n \\\"status\\\": \\\"green\\\",\\n \\\"symptom\\\": \\\"The cluster has enough room to add new shards.\\\",\\n \\\"details\\\": {\\n \\\"data\\\": {\\n \\\"max_shards_in_cluster\\\": 2000\\n },\\n \\\"frozen\\\": {\\n \\\"max_shards_in_cluster\\\": 0\\n }\\n }\\n },\\n \\\"ilm\\\": {\\n \\\"status\\\": \\\"green\\\",\\n \\\"symptom\\\": \\\"Index Lifecycle Management is running\\\",\\n \\\"details\\\": {\\n \\\"policies\\\": 29,\\n \\\"stagnating_indices\\\": 0,\\n \\\"ilm_status\\\": \\\"RUNNING\\\"\\n }\\n },\\n \\\"slm\\\": {\\n \\\"status\\\": \\\"green\\\",\\n \\\"symptom\\\": \\\"Snapshot Lifecycle Management is running\\\",\\n \\\"details\\\": {\\n \\\"slm_status\\\": \\\"RUNNING\\\",\\n \\\"policies\\\": 1\\n }\\n }\\n }\\n}\\nLogs (if relevant)\\nAfter setting the logger.org.elasticsearch.health.node to DEBUG and restarting the current master (instance 0 in our example), the below DEBUG logs were observed:\\n\\n | 28 Aug, 2023 @ 09:33:08.070 | [instance-0000000000] Resetting the health monitoring because the master node changed, current health node is null.\\n\\n | 28 Aug, 2023 @ 09:30:55.653 | [instance-0000000001] Resetting the health monitoring because the master node changed, current health node is null.\\n\\n | 28 Aug, 2023 @ 09:30:55.145 | [tiebreaker-0000000002] Resetting the health monitoring because the master node changed, current health node is null. \\n\\n | 28 Aug, 2023 @ 09:30:54.647 | [instance-0000000001] Resetting the health monitoring because the master node changed, current health node is null\\n\\n | 28 Aug, 2023 @ 09:30:54.630 | [tiebreaker-0000000002] Resetting the health monitoring because the master node changed, current health node is null", "branch": "cca26276b3965e24da9367c0ccfde411ec5124cd", "issue_url": "https://github.com/elastic/elasticsearch/issues/98926", "fix_url": "https://github.com/elastic/elasticsearch/pull/105449", "issue_created": "2023-08-28", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": true, "analysis_removed": "No", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "elasticsearch-105065", "system": "elasticsearch", "issue_number": "105065", "lite": false, "title": "Avoid race in LocalHealthMonitor w.r.t null values", "description": "There is a race condition in the LocalHealthMonitor regarding null values (i.e. initial/reset values):\n\nLast reported value was null\nthere is new a health node\nNew run starts the update process and records previous value null\nhealth node/master change\nnew reported value is null\nRun sees null and considers that it's ok to update the value....\nCan probably relatively easily be fixed by using some form of ref counting/versioning of the lastReportedValue", "branch": "bb1eddada3678257838b0590090ff9eb68acaa1b", "issue_url": "https://github.com/elastic/elasticsearch/issues/105065", "fix_url": "https://github.com/elastic/elasticsearch/pull/105674", "issue_created": "2024-02-02", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-110360", "system": "elasticsearch", "issue_number": "110360", "lite": false, "title": "PlainActionFuture#assertCompleteAllowed false positives on concurrent resolve", "description": "PlainActionFuture detects dangerous usage patterns where threads from the same pool are simultaneously resolving and waiting on the future. This is to prevent tests that deadlock and is only switched on when assertions are enabled.\n\nThis deadlock detection can falsely fire when threads from the same pool are simultaneously resolving a future.\n\nThe sequence of events is as follows:\n\nT1 calls PlainActionFuture.Sync.complete with a value or exception, it successfully performs compareAndSet(RUNNING, COMPLETING) and proceeds to set the value/exception.\nT2 calls PlainActionFuture.Sync.complete with a value or exception, if fails to perform compareAndSet(RUNNING, COMPLETING) while state is COMPLETING. It calls awaitShared to wait for T1 to finish.\nT3 from the same pool as T2 attempts to complete the future, it throws in assertCompleteAllowed because there is a thread from the same pool (T2) waiting on the result.\nThis is a false-positive because T2 will definitely complete.\n\nNote that T1 can be the same as T3 if completing the future in a loop or the thread gets recycled.\n\nSteps to Reproduce\nThis has resulted in at least one test flake\n\n", "branch": "89cd966b247148372aed73c3586b0754d6e176ca", "issue_url": "https://github.com/elastic/elasticsearch/issues/110360", "fix_url": "https://github.com/elastic/elasticsearch/pull/110361", "issue_created": "2024-07-02", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-113615", "system": "elasticsearch", "issue_number": "113615", "lite": false, "title": "Elasticsearch accepts script processors that are strings and not map", "description": "When creating an Ingest Pipeline, it's currently possible to create a processor, which is not a map:\nPUT _ingest/pipeline/test\n{\n \"processors\": [\n {\n \"script\": \"\"\"ctx.test=2;\"\"\"\n }\n ]\n}\nThis is accepted by Elasticsearch, however, the expected syntax should be:\n\nPUT _ingest/pipeline/test\n{\n \"processors\": [\n {\n \"script\": {\n \"source\": \"ctx.test=2;\"\n }\n }\n ]\n}\nThis causes API GET _ml/trained_models/_stats (which iterates over all processors and verify that they are maps) to fail with the error:\n\n[2024-09-26T09:55:24,326][WARN ][o.e.x.m.MachineLearningUsageTransportAction] [node-1] Failed to get inference usage to include in ML usage\njava.lang.ClassCastException: class java.lang.String cannot be cast to class java.util.Map (java.lang.String and java.util.Map are in module java.base of loader 'bootstrap')\nI would expected Elasticsearch to refuse processors that are not Maps.", "branch": "b2a69b54e1f28711d423926d9261a8346fd22c76", "issue_url": "https://github.com/elastic/elasticsearch/issues/113615", "fix_url": "https://github.com/elastic/elasticsearch/pull/113697", "issue_created": "2024-09-26", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "elasticsearch-116341", "system": "elasticsearch", "issue_number": "116341", "lite": false, "title": "Async search can throw NPE from onClusterResponseMinimizeRoundtrips", "description": "Stack trace seen from a customer environment:\n\n`[2024-10-23T13:34:32,289][WARN ][o.e.a.s.SearchProgressListener] [data-2] [ibprod_azure] Failed to execute progress listener onResponseMinimizeRoundtrips\njava.lang.NullPointerException: Cannot invoke \"org.elasticsearch.xpack.search.MutableSearchResponse.updateResponseMinimizeRoundtrips(String, org.elasticsearch.action.search.SearchResponse)\" because the return value of \"org.apache.lucene.util.SetOnce.get()\" is null\nat org.elasticsearch.xpack.search.AsyncSearchTask$Listener.onClusterResponseMinimizeRoundtrips(AsyncSearchTask.java:512) ~[?:?]\nat org.elasticsearch.action.search.SearchProgressListener.notifyClusterResponseMinimizeRoundtrips(SearchProgressListener.java:181) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.action.search.TransportSearchAction$3.innerOnResponse(TransportSearchAction.java:781) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.action.search.TransportSearchAction$3.innerOnResponse(TransportSearchAction.java:776) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.action.search.TransportSearchAction$CCSActionListener.onResponse(TransportSearchAction.java:1487) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.action.ActionListenerResponseHandler.handleResponse(ActionListenerResponseHandler.java:48) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.transport.TransportService$UnregisterChildTransportResponseHandler.handleResponse(TransportService.java:1742) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleResponse(TransportService.java:1465) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleResponse(TransportService.java:1465) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.transport.InboundHandler.doHandleResponse(InboundHandler.java:433) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.transport.InboundHandler$2.doRun(InboundHandler.java:390) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:33) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:984) ~[elasticsearch-8.13.4.jar:?]\nat org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26) ~[elasticsearch-8.13.4.jar:?]\nat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]\nat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]\nWe need to try to reproduce it but this will happen when AsyncSearchTask.onListShards is not called (initializing the MutableSearchResponse in that class) before AsyncSearchTask.onClusterResponseMinimizeRoundtrips is called. At a minimum we need to add some defensive programming in the latter method. Optimally we will find why onListShards is not getting called (or perhaps not succeeding) for this case and fix the underlying issue.", "branch": "a4482d4c4c2d24418553510afa6a11a5f316983a", "issue_url": "https://github.com/elastic/elasticsearch/issues/116341", "fix_url": "https://github.com/elastic/elasticsearch/pull/117504", "issue_created": "2024-09-06", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "elasticsearch-128583", "system": "elasticsearch", "issue_number": "128583", "lite": true, "title": "TransportIndicesStatsAction causes starvation of tasks on management thread pool due to Engine.getSparseVectorValueCount", "description": "Engine.getSparseVectorValueCount might block 100% of the management threads in case we're facing frequent cache misses.\nThis causes the thread pool to queue and potentially starve important other work that's also depending on the management thread pool.\nThis was discovered on an internal serverless project.", "branch": "041c42a77961b2a227e2631d2d4034d2716779c4", "issue_url": "https://github.com/elastic/elasticsearch/issues/128583", "fix_url": "https://github.com/elastic/elasticsearch/pull/128740", "issue_created": "2025-05-28", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 1} {"instance_id": "elasticsearch-128852", "system": "elasticsearch", "issue_number": "128852", "lite": true, "title": "ConcurrentModificationException in TransportClusterStatsAction", "description": "This error occurs:\n\n java.util.ConcurrentModificationException\n at java.base/java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1096)\n at java.base/java.util.ArrayList$Itr.next(ArrayList.java:1050)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.admin.cluster.stats.VersionStats.of(VersionStats.java:53)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.admin.cluster.stats.TransportClusterStatsAction.lambda$newResponseAsync$0(TransportClusterStatsAction.java:209)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.ActionListenerImplementations$MappedActionListener.onResponse(ActionListenerImplementations.java:105)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.SubscribableListener$SuccessResult.complete(SubscribableListener.java:401)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.SubscribableListener.tryComplete(SubscribableListener.java:321)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.SubscribableListener.addListener(SubscribableListener.java:217)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.SubscribableListener.addListener(SubscribableListener.java:175)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.SubscribableListener.lambda$andThenApply$2(SubscribableListener.java:535)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.ActionListener.run(ActionListener.java:465)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.SubscribableListener.newForked(SubscribableListener.java:133)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.SubscribableListener.andThenApply(SubscribableListener.java:535)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.admin.cluster.stats.TransportClusterStatsAction.newResponseAsync(TransportClusterStatsAction.java:186)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.admin.cluster.stats.TransportClusterStatsAction.newResponseAsync(TransportClusterStatsAction.java:82)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.nodes.TransportNodesAction$1.lambda$onCompletion$4(TransportNodesAction.java:167)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.nodes.TransportNodesAction.lambda$doExecute$0(TransportNodesAction.java:179)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.ActionListenerImplementations$ResponseWrappingActionListener.onResponse(ActionListenerImplementations.java:261)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.action.support.ThreadedActionListener$1.doRun(ThreadedActionListener.java:40)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:1044)\n at org.elasticsearch.server@9.1.0/org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:27)\n at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1095)\n at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:619)\n at java.base/java.lang.Thread.run(Thread.java:1447)", "branch": "c17bfcbfc219f1a0746baaf3b9501b2e479488a4", "issue_url": "https://github.com/elastic/elasticsearch/issues/128852", "fix_url": "https://github.com/elastic/elasticsearch/pull/130303", "issue_created": "2025-06-03", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "elasticsearch-134925", "system": "elasticsearch", "issue_number": "134925", "lite": false, "title": "Transforms will infinitely queue PIT closures causing a \"PIT storm\"", "description": "Transforms when using point-in-time (PIT) search will create multiple PITs over the lifetime of a single transform pivot page.\n\nIf there is any failure, or a new search is initiated, or the scheduled pivot completes, it will request the PITs to be deleted.\n\nHowever, it will not wait for these PITs to be deleted before scheduling again or continuing with another set of searches. Consequently, its possible for many transforms, in quick succession, could create MANY PITs and cause a significant queue of close pit requests which can cause pressure on the system.\n\nTransforms should wait for all its close-pit requests to complete before continuing its execution paths. Since close-pit \"should\" be fast, this should be OK. However, if close pit is slow, we want transforms to be naturally throttled to prevent a PIT storm.", "branch": "1904abbb730ec6bfc47a58425a3949664013ed55", "issue_url": "https://github.com/elastic/elasticsearch/issues/134925", "fix_url": "https://github.com/elastic/elasticsearch/pull/134955", "issue_created": "2025-09-17", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-135472", "system": "elasticsearch", "issue_number": "135472", "lite": true, "title": "GroupShardsIterator can significantly tie up transport workers", "description": "When querying many shards, it has been observed that iterating the shards themselves can end up tying up a transport_worker thread. I am not sure if we want to optimize this path further or pivot to a different thread when above some shard threshold.\n\nSwitching to another threadpool on few shards (<10k?) seems unhelpful.", "branch": "8a38cbbafee64879a0fd20ce16e8546f30057cee", "issue_url": "https://github.com/elastic/elasticsearch/issues/135472", "fix_url": "https://github.com/elastic/elasticsearch/pull/140747", "issue_created": "2025-09-25", "severity": "Major", "root_cause_type": "Performance", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-139252", "system": "elasticsearch", "issue_number": "139252", "lite": true, "title": "TransportGetTransformStatsAction can eat a transport thread, causing cluster instability", "description": "Transform stats does a fair bit of work just sitting in direct executor. This is not good. Depending on the scale of the cluster, if multiple users call the stats call for transforms, it could disconnect node from a cluster.\n\nWe should:\n\nMake this way way cheaper, only consider transform tasks (do filtering directly in tasks request, not after gathering all tasks on the node) and be careful about ginormous strings being created and concatenated\nConsider moving this off of direct executor.\nSome additional notes:\n\nThis is 100% a bug that needs reporting to the transform (ML?) folks. We seem to be looping over all tasks, filtering them by description (not even filtering by action first??). Building the description of a single search task might not be too costly but isn't exactly free either, and building a description of them all could be very expensive, and even worse I'm pretty sure no search tasks could possibly have a matching description anyway. Moreover this is all happening on the transport_worker for no good reason and needs to be moved elsewhere as a matter of some urgency.\n", "branch": "8a3da5e87351f09306f75b74d29ce4ea1d80d28e", "issue_url": "https://github.com/elastic/elasticsearch/issues/139252", "fix_url": "https://github.com/elastic/elasticsearch/pull/139857", "issue_created": "2025-12-09", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-140492", "system": "elasticsearch", "issue_number": "140492", "lite": false, "title": "NPE causing doc-level indexing failure in TSDB data stream", "description": "See e.g.:\n\nIntake build failure\nLocal repro with extra logging\n[2026-01-10T12:03:31,063][DEBUG][o.e.i.s.IndexingFailuresDebugListener] [test-cluster-0] index-fail [KCjEJ9R_BgO8TRX2QOd6dpR12oDh--qoyNZRQPy43y34Qdy2dpsyG0p___5kWKOUA7NNlnE] seq# [-2] allocation-id [[id=9ulrOz6xSemJQsht2vH7OQ]] primaryTerm [1] operationPrimaryTerm [1] origin [PRIMARY] java.lang.NullPointerException: Cannot invoke \"org.apache.lucene.util.AttributeImpl.end()\" because \"state.attribute\" is null\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.util.AttributeSource.endAttributes(AttributeSource.java:284)\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.analysis.TokenStream.end(TokenStream.java:163)\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.index.IndexingChain$PerField.invertTokenStream(IndexingChain.java:1326)\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.index.IndexingChain$PerField.invert(IndexingChain.java:1196)\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.index.IndexingChain.processField(IndexingChain.java:741)\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.index.IndexingChain.processDocument(IndexingChain.java:618)\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.index.DocumentsWriterPerThread.updateDocuments(DocumentsWriterPerThread.java:274)\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.index.DocumentsWriter.updateDocuments(DocumentsWriter.java:425)\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.index.IndexWriter.updateDocuments(IndexWriter.java:1573)\t\n\tat org.apache.lucene.core@10.3.2/org.apache.lucene.index.IndexWriter.addDocuments(IndexWriter.java:1531)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.index.engine.InternalEngine.addDocs(InternalEngine.java:1529)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.index.engine.InternalEngine.indexIntoLucene(InternalEngine.java:1460)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.index.engine.InternalEngine.index(InternalEngine.java:1262)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.index.shard.IndexShard.index(IndexShard.java:1142)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.index.shard.IndexShard.applyIndexOperation(IndexShard.java:1052)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.index.shard.IndexShard.applyIndexOperationOnPrimary(IndexShard.java:970)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.action.bulk.TransportShardBulkAction.executeBulkItemRequest(TransportShardBulkAction.java:441)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.action.bulk.TransportShardBulkAction$2.doRun(TransportShardBulkAction.java:291)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:27)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.action.bulk.TransportShardBulkAction.performOnPrimary(TransportShardBulkAction.java:359)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.action.bulk.TransportShardBulkAction.dispatchedShardOperationOnPrimary(TransportShardBulkAction.java:196)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.action.bulk.TransportShardBulkAction.dispatchedShardOperationOnPrimary(TransportShardBulkAction.java:83)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.action.support.replication.TransportWriteAction$1.doRun(TransportWriteAction.java:245)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:27)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:35)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:1113)\t\n\tat org.elasticsearch.server@9.4.0-SNAPSHOT/org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:27)\t\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)\t\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)\t\n\tat java.base/java.lang.Thread.run(Thread.java:1474)\nIt seems that this failure started happening when #138678 was merged: at least, so far I've seen 15 failures out of 383 runs (3.9% failure rate) on 980247c, but zero failures out of 244 runs on its predecessor 56a8d1c.\n\n", "branch": "21fc8565454e1cea03fa7276dcb550f6a2bf6ec8", "issue_url": "https://github.com/elastic/elasticsearch/issues/140492", "fix_url": "https://github.com/elastic/elasticsearch/pull/140556", "issue_created": "2026-01-10", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": true, "analysis_removed": "No", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "elasticsearch-141740", "system": "elasticsearch", "issue_number": "141740", "lite": false, "title": "Logging cancellation task with large number of nodes/actions", "description": "When canceling a possibly large list of actions / tasks, a possibly large amount of memory might be consumed at times as ES tries to log it by means of its description CancelTasksRequest#getDescription.\nWe should probably make sure the size of the underlying arrays doesn't become too big, and return a subset of the actions/nodes in the description when that's the case.\n\n", "branch": "96be973fb5687c9837f51352fd7c8c5d2a5894aa", "issue_url": "https://github.com/elastic/elasticsearch/issues/141740", "fix_url": "https://github.com/elastic/elasticsearch/pull/141815", "issue_created": "2026-02-03", "severity": "Major", "root_cause_type": "Performance", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "elasticsearch-147171", "system": "elasticsearch", "issue_number": "147171", "lite": false, "title": "[CI] OperatorPrivilegesIT testNonOperatorUserCanCallAnalyzeRepositoryAPI failing", "description": "Reproduction Line: ./gradlew ':x-pack:plugin:security:qa:operator-privileges-tests:javaRestTest' --tests 'org.elasticsearch.xpack.security.operator.OperatorPrivilegesIT.testNonOperatorUserCanCallAnalyzeRepositoryAPI' -Dtests.seed=7604F88DC268C48D -Dtests.locale=hsb -Dtests.timezone=Europe/London -Druntime.java=26\nApplicable branches: main\nReproduces locally?: N/A\nFailure History: See dashboard\nFailure Message: org.elasticsearch.client.ResponseException: method [POST], host [http://[::1]:33965], URI [/_snapshot/testAnalysisRepo/_analyze], status line [HTTP/1.1 500 Internal Server Error] {\"error\":{\"root_cause\":[{\"type\":\"repository_verification_exception\",\"reason\":\"[testAnalysisRepo] multiple writes succeeded to overwrite-protected blob temp-analysis-4mmA0_dGQbu0hOK1Zb-j6A/test-overwrite-blob-Qkt1E-vDRhiz723tAxQPVA\",\"suppressed\":[{\"type\":\"repository_verification_exception\",\"reason\":\"[testAnalysisRepo] failure processing [blob analysis [testAnalysisRepo:temp-analysis-4mmA0_dGQbu0hOK1Zb-j6A/test-blob-98-wMWgzgtST0a3eA4RDMXH1A, length=32, seed=-1681044207315830571, readEarly=false, writeAndOverwrite=false, abortWrite=false, copyBlobName=null]]\"}]}],\"type\":\"repository_verification_exception\",\"reason\":\"[testAnalysisRepo] Elasticsearch observed the storage system underneath this repository behaved incorrectly which indicates it is not suitable for use with Elasticsearch snapshots. See [https://www.el\n[truncated]\nIssue Reasons: [main] 1 consecutive failures in test testNonOperatorUserCanCallAnalyzeRepositoryAPI [main] 1 consecutive failures in step part4 [main] 1 consecutive failures in pipeline elasticsearch-intake [main] 15 failures in test testNonOperatorUserCanCallAnalyzeRepositoryAPI (1.7% fail rate in 884 executions) [main] 10 failures in step part-4 (1.8% fail rate in 557 executions) [main] 9 failures in pipeline elasticsearch-pull-request (1.6% fail rate in 548 executions) [main] 2 failures in pipeline elasticsearch-periodic-java-ea (66.7% fail rate in 3 executions) [main] 2 failures in pipeline elasticsearch-periodic-platform-support (100.0% fail rate in 2 executions)\nNote: This issue was created using new test triage automation. Please report issues or feedback to es-delivery.\n", "branch": "2a88d3a56c5afdb7a1f30e860a38c0b28ddb3f58", "issue_url": "https://github.com/elastic/elasticsearch/issues/147171", "fix_url": "https://github.com/elastic/elasticsearch/pull/147405", "issue_created": "2026-04-22", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "etcd-5664", "system": "etcd", "issue_number": "5664", "lite": false, "title": "raft: state.commit is out of range", "description": "via local-tester with reordering:\n\n```\n2016-06-13 17:47:28.006281 I | etcdmain: etcd Version: 3.0.0-beta.0+git\n2016-06-13 17:47:28.006332 I | etcdmain: Git SHA: 65e19a1\n2016-06-13 17:47:28.006337 I | etcdmain: Go Version: go1.6\n2016-06-13 17:47:28.006348 I | etcdmain: Go OS/Arch: linux/amd64\n2016-06-13 17:47:28.006353 I | etcdmain: setting maximum number of CPUs to 8, total number of available CPUs is 8\n2016-06-13 17:47:28.006359 W | etcdmain: no data-dir provided, using default data-dir ./infra1.etcd\n2016-06-13 17:47:28.006391 N | etcdmain: the server is already initialized as member before, starting as etcd member... \n2016-06-13 17:47:28.006451 I | etcdmain: listening for peers on http://127.0.0.1:12380\n2016-06-13 17:47:28.006474 I | etcdmain: listening for client requests on 127.0.0.1:11119 \n2016-06-13 17:47:28.013070 I | etcdserver: recovered store from snapshot at index 38626 \n2016-06-13 17:47:28.013081 I | etcdserver: name = infra1\n2016-06-13 17:47:28.013087 I | etcdserver: data dir = infra1.etcd \n2016-06-13 17:47:28.013093 I | etcdserver: member dir = infra1.etcd/member\n2016-06-13 17:47:28.013098 I | etcdserver: heartbeat = 100ms\n2016-06-13 17:47:28.013104 I | etcdserver: election = 1000ms\n2016-06-13 17:47:28.013109 I | etcdserver: snapshot count = 1000\n2016-06-13 17:47:28.013118 I | etcdserver: advertise client URLs = http://127.0.0.1:2379\n2016-06-13 17:47:28.065753 I | etcdserver: restarting member 5da0b1f0ade347d1 in cluster ea3db81f3897e3ad at commit index 38040\n2016-06-13 17:47:28.065854 C | raft: 5da0b1f0ade347d1 state.commit 38040 is out of range [38626, 38626]\npanic: \n5da0b1f0ade347d1 state.commit 38040 is out of range [38626, 38626]\ngoroutine 1 [running]:\npanic(0xcd2fa0, 0xc8205ff170) \n /usr/lib/go/src/runtime/panic.go:464 +0x3e6\ngithub.com/coreos/etcd/cmd/vendor/github.com/coreos/pkg/capnslog.(*PackageLogger).Panicf(0xc82010d100, 0x119e200, 0x2b, 0xc8204a5d40, 0x4, 0x4)\n /home/anthony/go/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/pkg/capnslog/pkg_logger.go:73 +0x191\ngithub.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/raft.(*raft).loadState(0xc820204340, 0x67a, 0xd2643f51f16cc22b, 0x9498, 0x0, 0x0, 0x0)\n /home/anthony/go/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/raft/raft.go:942 +0x2a2\ngithub.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/raft.newRaft(0xc8201f7b30, 0x451b20)\n /home/anthony/go/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/raft/raft.go:225 +0x8ff\ngithub.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/raft.RestartNode(0xc8201f7b30, 0x0, 0x0)\n /home/anthony/go/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/raft/node.go:212 +0x45\ngithub.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdserver.restartNode(0xc8202163c0, 0xc820208990, 0x29, 0xc8201f7f68, 0x0, 0x0, 0x0, 0x0)\n /home/anthony/go/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdserver/raft.go:361 +0x7c7\ngithub.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdserver.NewServer(0xc8202163c0, 0x0, 0x0, 0x0)\n /home/anthony/go/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdserver/server.go:350 +0x3cf2\ngithub.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain.startEtcd(0xc820160800, 0x0, 0x0, 0x0)\n /home/anthony/go/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain/etcd.go:366 +0x23ea\ngithub.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain.startEtcdOrProxyV2()\n /home/anthony/go/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain/etcd.go:116 +0x213d\ngithub.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain.Main()\n /home/anthony/go/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain/main.go:36 +0x21e\nmain.main()\n /home/anthony/go/src/github.com/coreos/etcd/cmd/main.go:28 +0x14\nTerminating etcd1\n```\n\n", "branch": "b07fbbf27cfb2d5d9e209e198eb056c9ff12613f", "issue_url": "https://github.com/etcd-io/etcd/issues/5664", "fix_url": "https://github.com/etcd-io/etcd/pull/5690", "issue_created": "2016-06-14", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "etcd-14110", "system": "etcd", "issue_number": "14110", "lite": false, "title": "panic: unexpected error during txn", "description": "### What happened?\n\nIn a Jepsen test run of five etcd 3.5.3 nodes, with process pauses (sending processes SIGSTOP and SIGCONT), compaction (performed via the admin API), and defragmentation (via etcdctl), one etcd process crashed with the following error message:\n\n```\n{\"level\":\"panic\",\"ts\":\"2022-06-13T14:11:27.870Z\",\"caller\":\"etcdserver/apply.go:638\",\"msg\":\"unexpected error during txn\",\"error\":\"context canceled\",\"stacktrace\":\"go.etcd.io/etcd/server/v3/etcdserver.(*applierV3backend).applyTxn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/apply.go:638\\ngo.etcd.io/etcd/server/v3/etcdserver.(*applierV3backend).Txn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/apply.go:477\\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).Txn.func3\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:181\\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).doSerialize\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:659\\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).Txn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:182\\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.(*kvServer).Txn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/key.go:95\\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.(*quotaKVServer).Txn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/quota.go:70\\ngo.etcd.io/etcd/api/v3/etcdserverpb._KV_Txn_Handler.func1\\n\\t/go/src/go.etcd.io/etcd/release/etcd/api/etcdserverpb/rpc.pb.go:6617\\ngithub.com/grpc-ecosystem/go-grpc-prometheus.(*ServerMetrics).UnaryServerInterceptor.func1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-prometheus@v1.2.0/server_metrics.go:107\\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25\\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.newUnaryInterceptor.func1\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/interceptor.go:71\\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25\\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.newLogUnaryInterceptor.func1\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/interceptor.go:78\\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25\\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:34\\ngo.etcd.io/etcd/api/v3/etcdserverpb._KV_Txn_Handler\\n\\t/go/src/go.etcd.io/etcd/release/etcd/api/etcdserverpb/rpc.pb.go:6619\\ngoogle.golang.org/grpc.(*Server).processUnaryRPC\\n\\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1286\\ngoogle.golang.org/grpc.(*Server).handleStream\\n\\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1609\\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.2\\n\\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:934\"}\n{\"level\":\"info\",\"ts\":\"2022-06-13T14:11:27.875Z\",\"caller\":\"traceutil/trace.go:171\",\"msg\":\"trace[430686560] transaction\",\"detail\":\"{read_only:true; }\",\"duration\":\"5.770188852s\",\"start\":\"2022-06-13T14:11:22.105Z\",\"end\":\"2022-06-13T14:11:27.875Z\",\"steps\":[\"trace[430686560] 'agreement among raft nodes before linearized reading' (duration: 5.763577986s)\"],\"step_count\":1}\npanic: unexpected error during txn\n\ngoroutine 10896 [running]:\ngo.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc00011ec00, 0xc0035542c0, 0x1, 0x1)\n\t/go/pkg/mod/go.uber.org/zap@v1.17.0/zapcore/entry.go:234 +0x58d\ngo.uber.org/zap.(*Logger).Panic(0xc00048c280, 0x1220287, 0x1b, 0xc0035542c0, 0x1, 0x1)\n\t/go/pkg/mod/go.uber.org/zap@v1.17.0/logger.go:227 +0x85\ngo.etcd.io/etcd/server/v3/etcdserver.(*applierV3backend).applyTxn(0xc00000d1e8, 0x13a1cb8, 0xc002fe7cb0, 0x13ab818, 0xc003cfe550, 0xc003d07030, 0xc003b2ab00, 0x1, 0x1, 0xc003cec730, ...)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/apply.go:638 +0x930\ngo.etcd.io/etcd/server/v3/etcdserver.(*applierV3backend).Txn(0xc00000d1e8, 0x13a1cb8, 0xc002fe7cb0, 0xc003d07030, 0x2, 0x48, 0x493c26, 0x2)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/apply.go:477 +0x38a\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).Txn.func3()\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:181 +0x70\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).doSerialize(0xc000442a00, 0x13a1cb8, 0xc002fe7cb0, 0xc0030314a8, 0xc0030314d8, 0xc003e1c500, 0x0)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:659 +0xf8\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).Txn(0xc000442a00, 0x13a1cb8, 0xc002fe7cb0, 0xc003d07030, 0x0, 0x0, 0x0)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:182 +0x40e\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.(*kvServer).Txn(0xc000324fc0, 0x13a1cb8, 0xc002fe7b60, 0xc003d07030, 0xc003d07030, 0x0, 0x0)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/key.go:95 +0xfc\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.(*quotaKVServer).Txn(0xc000325000, 0x13a1cb8, 0xc002fe7b60, 0xc003d07030, 0xc000325000, 0x13a8a68, 0xc0002b7e60)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/quota.go:70 +0xc2\ngo.etcd.io/etcd/api/v3/etcdserverpb._KV_Txn_Handler.func1(0x13a1cb8, 0xc002fe7b60, 0x11b1020, 0xc003d07030, 0x14, 0xc003b89d60, 0x2, 0xc0000f2818)\n\t/go/src/go.etcd.io/etcd/release/etcd/api/etcdserverpb/rpc.pb.go:6617 +0x89\ngithub.com/grpc-ecosystem/go-grpc-prometheus.(*ServerMetrics).UnaryServerInterceptor.func1(0x13a1cb8, 0xc002fe7b60, 0x11b1020, 0xc003d07030, 0xc003a7bac0, 0xc003a718a8, 0xc003d746e0, 0x0, 0x0, 0x0)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-prometheus@v1.2.0/server_metrics.go:107 +0xb0\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1(0x13a1cb8, 0xc002fe7b60, 0x11b1020, 0xc003d07030, 0x1ab2d20, 0xc000437200, 0x8bda0c, 0x13881c0)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25 +0x63\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.newUnaryInterceptor.func1(0x13a1cb8, 0xc002fe7b60, 0x11b1020, 0xc003d07030, 0xc003a7bac0, 0xc003a7bae0, 0x493c26, 0x62a7458a, 0x6450608, 0x3bbfb531619)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/interceptor.go:71 +0x15c\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1(0x13a1cb8, 0xc002fe7b60, 0x11b1020, 0xc003d07030, 0x0, 0x203000, 0x13b1c70, 0xc003e10710)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25 +0x63\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.newLogUnaryInterceptor.func1(0x13a1cb8, 0xc002fe7b60, 0x11b1020, 0xc003d07030, 0xc003a7bac0, 0xc003a7bb00, 0x0, 0x0, 0x0, 0x0)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/interceptor.go:78 +0xd9\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1(0x13a1cb8, 0xc002fe7b60, 0x11b1020, 0xc003d07030, 0xc00021c800, 0x0, 0xc0000f2b30, 0x40e318)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25 +0x63\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1(0x13a1cb8, 0xc002fe7b60, 0x11b1020, 0xc003d07030, 0xc003a7bac0, 0xc003a718a8, 0xc0000f2ba0, 0x573fa6, 0x1158b40, 0xc002fe7b60)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:34 +0xd7\ngo.etcd.io/etcd/api/v3/etcdserverpb._KV_Txn_Handler(0x10fa540, 0xc000325000, 0x13a1cb8, 0xc002fe7b60, 0xc003e18000, 0xc0003098c0, 0x13a1cb8, 0xc002fe7b60, 0xc003a9f640, 0x9)\n\t/go/src/go.etcd.io/etcd/release/etcd/api/etcdserverpb/rpc.pb.go:6619 +0x150\ngoogle.golang.org/grpc.(*Server).processUnaryRPC(0xc0004e7340, 0x13ae2d8, 0xc00379ec00, 0xc003e17200, 0xc000309a10, 0x1a6e268, 0x0, 0x0, 0x0)\n\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1286 +0x52b\ngoogle.golang.org/grpc.(*Server).handleStream(0xc0004e7340, 0x13ae2d8, 0xc00379ec00, 0xc003e17200, 0x0)\n\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1609 +0xd0c\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.2(0xc002a90770, 0xc0004e7340, 0x13ae2d8, 0xc00379ec00, 0xc003e17200)\n\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:934 +0xab\ncreated by google.golang.org/grpc.(*Server).serveStreams.func1\n\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:932 +0x1fd\n```\n\nThis is the first time this has cropped up, so I'm not sure whether pauses, compaction, and defrag are all necessary to trigger the bug. The only nemesis operations on this particular node before the crash appear to be pause & resume, but I imagine it's possible that other nodes performing compaction or defragmentation might have caused them to exchange (or fail to exchange!) messages with this node which caused it to crash\n\nHere's the full logs and data files from the cluster: [20220613T140950.000Z.zip](https://github.com/etcd-io/etcd/files/8891972/20220613T140950.000Z.zip).\n\n### What did you expect to happen?\n\nI expected etcd not to crash.\n\n### How can we reproduce it (as minimally and precisely as possible)?\n\nCheck out [jepsen-etcd](https://github.com/jepsen-io/etcd) 84d7d54698c387ed467dd5dfb8ca4bebc2ee46d5, and with a five-node cluster, run:\n\n```\nlein run test-all --username admin --nodes-file /home/admin/nodes --concurrency 4n --rate 500 --time-limit 300 --workload append --nemesis pause,admin --test-count 20\n```\n\nI'm not sure how long this will take to reproduce yet--still collecting evidence.\n\n### Anything else we need to know?\n\n_No response_\n\n### Etcd version (please run commands below)\n\n
\n\n```console\n$ etcd --version\netcd Version: 3.5.3\nGit SHA: 0452feec7\nGo Version: go1.16.15\nGo OS/Arch: linux/amd64\n\n$ etcdctl version\netcdctl version: 3.5.3\nAPI version: 3.5\n```\n\n
\n\n\n### Etcd configuration (command line flags or environment variables)\n\n
\netcd --enable-v2 --log-outputs stderr --logger zap --name n1 --listen-peer-urls http://192.168.122.101:2380/ --listen-client-urls http://192.168.122.101:2379/ --advertise-client-urls http://192.168.122.101:2379/ --initial-cluster-state new --initial-advertise-peer-urls http://192.168.122.101:2380/ --initial-cluster n1=[http://192.168.122.101:2380,n2=http://192.168.122.102:2380,n3=http://192.168.122.103:2380,n4=http://192.168.122.104:2380,n5=http://192.168.122.105:2380](http://192.168.122.101:2380%2Cn2%3Dhttp//192.168.122.102:2380,n3=http://192.168.122.103:2380,n4=http://192.168.122.104:2380,n5=http://192.168.122.105:2380) --snapshot-count 100 --experimental-initial-corrupt-check\n
\n\n\n### Etcd debug information (please run commands blow, feel free to obfuscate the IP address or FQDN in the output)\n\nThese node IDs aren't going to match, because I collected them from a different test run, but it should give you a general idea of the cluster topology:\n\n
\n\n```console\nadmin@ip-172-31-9-53:/opt/etcd$ ./etcdctl --endpoints http://172.31.9.53:2379 member list -w table\n+------------------+---------+--------------------------------------------+---------------------------+---------------------------+------------+\n| ID | STATUS | NAME | PEER ADDRS | CLIENT ADDRS | IS LEARNER |\n+------------------+---------+--------------------------------------------+---------------------------+---------------------------+------------+\n| 6f0318b69646b10a | started | ec2-54-234-45-183.compute-1.amazonaws.com | http://172.31.13.117:2380 | http://172.31.13.117:2379 | false |\n| 851bb95a115a0651 | started | ec2-54-90-123-74.compute-1.amazonaws.com | http://172.31.9.53:2380 | http://172.31.9.53:2379 | false |\n| 8ce655fee64e8888 | started | ec2-3-88-142-40.compute-1.amazonaws.com | http://172.31.7.132:2380 | http://172.31.7.132:2379 | false |\n| 9a228ee3e4899e1e | started | ec2-54-167-119-185.compute-1.amazonaws.com | http://172.31.9.60:2380 | http://172.31.9.60:2379 | false |\n| dfed32f696db96d2 | started | ec2-54-204-125-79.compute-1.amazonaws.com | http://172.31.12.135:2380 | http://172.31.12.135:2379 | false |\n+------------------+---------+--------------------------------------------+---------------------------+---------------------------+------------+\n\nadmin@ip-172-31-9-53:/opt/etcd$ {\"level\":\"warn\",\"ts\":\"2022-06-13T14:48:00.119Z\",\"logger\":\"etcd-client\",\"caller\":\"v3/retry_interceptor.go:62\",\"msg\":\"retrying of unary invoker failed\",\"target\":\"etcd-endpoints://0xc0004fa1c0/n1:2379\",\"attempt\":0,\"error\":\"rpc error: code = DeadlineExceeded desc = context deadline exceeded\"}\nFailed to get the status of endpoint http://n4:2379 (context deadline exceeded)\n+----------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+\n| ENDPOINT | ID | VERSION | DB SIZE | IS LEADER | IS LEARNER | RAFT TERM | RAFT INDEX | RAFT APPLIED INDEX | ERRORS |\n+----------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+\n| http://n1:2379 | 851bb95a115a0651 | 3.5.3 | 164 kB | false | false | 2 | 2302 | 2299 | |\n| http://n2:2379 | 6f0318b69646b10a | 3.5.3 | 164 kB | false | false | 3 | 2306 | 2306 | |\n| http://n5:2379 | 8ce655fee64e8888 | 3.5.3 | 168 kB | false | false | 3 | 4966 | 4966 | |\n+----------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+\n{\"level\":\"warn\",\"ts\":\"2022-06-13T14:47:38.147Z\",\"logger\":\"etcd-client\",\"caller\":\"v3/retry_interceptor.go:62\",\"msg\":\"retrying of unary invoker failed\",\"target\":\"etcd-endpoints://0xc0002fee00/n1:2379\",\"attempt\":0,\"error\":\"rpc error: code = DeadlineExceeded desc = context deadline exceeded\"}\nFailed to get the status of endpoint http://n4:2379 (cont\n```\n
\n\nNote that since these tests involve process pauses, it's tough to reach in and grab a coherent cluster view--pretty much every attempt I made involved timeouts.\n\n### Relevant log output\n\n_No response_\n\nI'm not sure if this is precisely the same bug or a different one, but I've managed to reproduce a crash with a slightly different error message purely from process pauses--no compaction or defrag operations involved. Here's the [full logs](http://jepsen.io.s3.amazonaws.com/analyses/etcd-3.5.3/20220613T174230.000Z.zip).\n\n```\n{\"level\":\"panic\",\"ts\":\"2022-06-13T17:45:54.601Z\",\"caller\":\"etcdserver/apply.go:638\",\"msg\":\"unexpected error during txn\",\"error\":\"context canceled\",\"stacktrace\":\"go.etcd.io/etcd/server/v3/etcdserver.(*applierV3backend).applyTxn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/apply.go:638\\ngo.etcd.io/etcd/server/v3/etcdserver.(*applierV3backend).Txn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/apply.go:477\\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).Txn.func3\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:181\\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).doSerialize\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:659\\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).Txn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:182\\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.(*kvServer).Txn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/key.go:95\\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.(*quotaKVServer).Txn\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/quota.go:70\\ngo.etcd.io/etcd/api/v3/etcdserverpb._KV_Txn_Handler.func1\\n\\t/go/src/go.etcd.io/etcd/release/etcd/api/etcdserverpb/rpc.pb.go:6617\\ngithub.com/grpc-ecosystem/go-grpc-prometheus.(*ServerMetrics).UnaryServerInterceptor.func1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-prometheus@v1.2.0/server_metrics.go:107\\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25\\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.newUnaryInterceptor.func1\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/interceptor.go:71\\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25\\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.newLogUnaryInterceptor.func1\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/interceptor.go:78\\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25\\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1\\n\\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:34\\ngo.etcd.io/etcd/api/v3/etcdserverpb._KV_Txn_Handler\\n\\t/go/src/go.etcd.io/etcd/release/etcd/api/etcdserverpb/rpc.pb.go:6619\\ngoogle.golang.org/grpc.(*Server).processUnaryRPC\\n\\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1286\\ngoogle.golang.org/grpc.(*Server).handleStream\\n\\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1609\\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.2\\n\\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:934\"}\n{\"level\":\"warn\",\"ts\":\"2022-06-13T17:45:54.603Z\",\"caller\":\"etcdserver/util.go:166\",\"msg\":\"apply request took too long\",\"took\":\"6.263437345s\",\"expected-duration\":\"100ms\",\"prefix\":\"read-only txn \",\"request\":\"compare:<> success: request_range: > failure:<>\",\"response\":\"\"}\n{\"level\":\"info\",\"ts\":\"2022-06-13T17:45:54.603Z\",\"caller\":\"traceutil/trace.go:171\",\"msg\":\"trace[2082798263] transaction\",\"detail\":\"{read_only:true; }\",\"duration\":\"6.26467016s\",\"start\":\"2022-06-13T17:45:48.338Z\",\"end\":\"2022-06-13T17:45:54.603Z\",\"steps\":[\"trace[2082798263] 'compare' (duration: 6.261489853s)\"],\"step_count\":1}\npanic: unexpected error during txn\n\ngoroutine 32669 [running]:\ngo.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc0030dda40, 0xc0031dbd40, 0x1, 0x1)\n\t/go/pkg/mod/go.uber.org/zap@v1.17.0/zapcore/entry.go:234 +0x58d\ngo.uber.org/zap.(*Logger).Panic(0xc00040c3c0, 0x1220287, 0x1b, 0xc0031dbd40, 0x1, 0x1)\n\t/go/pkg/mod/go.uber.org/zap@v1.17.0/logger.go:227 +0x85\ngo.etcd.io/etcd/server/v3/etcdserver.(*applierV3backend).applyTxn(0xc0003dc9d8, 0x13a1cb8, 0xc003c4e540, 0x13ab818, 0xc0031be650, 0xc002dc5f80, 0xc0028095f0, 0x1, 0x1, 0xc0032e0f50, ...)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/apply.go:638 +0x930\ngo.etcd.io/etcd/server/v3/etcdserver.(*applierV3backend).Txn(0xc0003dc9d8, 0x13a1cb8, 0xc003c4e540, 0xc002dc5f80, 0x2, 0x48, 0x493c26, 0x2)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/apply.go:477 +0x38a\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).Txn.func3()\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:181 +0x70\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).doSerialize(0xc000464300, 0x13a1cb8, 0xc003c4e540, 0xc0003094a8, 0xc0003094d8, 0xc0031f2d70, 0x0)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:659 +0xf8\ngo.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).Txn(0xc000464300, 0x13a1cb8, 0xc003c4e540, 0xc002dc5f80, 0x0, 0x0, 0x0)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/v3_server.go:182 +0x40e\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.(*kvServer).Txn(0xc0003ef300, 0x13a1cb8, 0xc003c4e3f0, 0xc002dc5f80, 0xc002dc5f80, 0x0, 0x0)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/key.go:95 +0xfc\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.(*quotaKVServer).Txn(0xc0003ef400, 0x13a1cb8, 0xc003c4e3f0, 0xc002dc5f80, 0xc0003ef400, 0x13a8a68, 0xc0002913e0)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/quota.go:70 +0xc2\ngo.etcd.io/etcd/api/v3/etcdserverpb._KV_Txn_Handler.func1(0x13a1cb8, 0xc003c4e3f0, 0x11b1020, 0xc002dc5f80, 0x14, 0xc0031f2b90, 0x2, 0xc000340818)\n\t/go/src/go.etcd.io/etcd/release/etcd/api/etcdserverpb/rpc.pb.go:6617 +0x89\ngithub.com/grpc-ecosystem/go-grpc-prometheus.(*ServerMetrics).UnaryServerInterceptor.func1(0x13a1cb8, 0xc003c4e3f0, 0x11b1020, 0xc002dc5f80, 0xc003228060, 0xc000627308, 0xc00046da20, 0x0, 0x0, 0x0)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-prometheus@v1.2.0/server_metrics.go:107 +0xb0\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1(0x13a1cb8, 0xc003c4e3f0, 0x11b1020, 0xc002dc5f80, 0x1ab2d20, 0xc00061e600, 0x8bda0c, 0x13881c0)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25 +0x63\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.newUnaryInterceptor.func1(0x13a1cb8, 0xc003c4e3f0, 0x11b1020, 0xc002dc5f80, 0xc003228060, 0xc003228080, 0x493c26, 0x62a777cc, 0x14323d4a, 0xf6fa2f301f7)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/interceptor.go:71 +0x15c\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1(0x13a1cb8, 0xc003c4e3f0, 0x11b1020, 0xc002dc5f80, 0x0, 0x203000, 0x13b1c70, 0xc0022fbc20)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25 +0x63\ngo.etcd.io/etcd/server/v3/etcdserver/api/v3rpc.newLogUnaryInterceptor.func1(0x13a1cb8, 0xc003c4e3f0, 0x11b1020, 0xc002dc5f80, 0xc003228060, 0xc0032280a0, 0x0, 0x0, 0x0, 0x0)\n\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/api/v3rpc/interceptor.go:78 +0xd9\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1.1.1(0x13a1cb8, 0xc003c4e3f0, 0x11b1020, 0xc002dc5f80, 0x1a82cc0, 0x0, 0xc000340b30, 0x40e318)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:25 +0x63\ngithub.com/grpc-ecosystem/go-grpc-middleware.ChainUnaryServer.func1(0x13a1cb8, 0xc003c4e3f0, 0x11b1020, 0xc002dc5f80, 0xc003228060, 0xc000627308, 0xc000340ba0, 0x573fa6, 0x1158b40, 0xc003c4e3f0)\n\t/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/chain.go:34 +0xd7\ngo.etcd.io/etcd/api/v3/etcdserverpb._KV_Txn_Handler(0x10fa540, 0xc0003ef400, 0x13a1cb8, 0xc003c4e3f0, 0xc0021f2000, 0xc0002f15f0, 0x13a1cb8, 0xc003c4e3f0, 0xc003a187c8, 0x14)\n\t/go/src/go.etcd.io/etcd/release/etcd/api/etcdserverpb/rpc.pb.go:6619 +0x150\ngoogle.golang.org/grpc.(*Server).processUnaryRPC(0xc000517340, 0x13ae2d8, 0xc00345d200, 0xc002529320, 0xc0002f1740, 0x1a6e268, 0x0, 0x0, 0x0)\n\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1286 +0x52b\ngoogle.golang.org/grpc.(*Server).handleStream(0xc000517340, 0x13ae2d8, 0xc00345d200, 0xc002529320, 0x0)\n\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:1609 +0xd0c\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.2(0xc003ca7820, 0xc000517340, 0x13ae2d8, 0xc00345d200, 0xc002529320)\n\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:934 +0xab\ncreated by google.golang.org/grpc.(*Server).serveStreams.func1\n\t/go/pkg/mod/google.golang.org/grpc@v1.38.0/server.go:932 +0x1fd\t\n```", "branch": "v3.5.3", "issue_url": "https://github.com/etcd-io/etcd/issues/14110", "fix_url": "https://github.com/etcd-io/etcd/pull/14149", "issue_created": "2022-06-13", "severity": "Critical", "root_cause_type": "Error handling", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "etcd-14325", "system": "etcd", "issue_number": "14325", "lite": false, "title": "Periodic corruption check doesn’t do anything after compaction", "description": "### What happened?\n\nAfter turning on `--experimental-corrupt-check-time`, I’ve noticed that any time there has been a compaction and no recent write to etcd, the corruption check fails to actually run. \r\n\r\nThe output on the leader is\r\n```\r\n{\"level\":\"info\",\"ts\":\"2022-08-02T17:55:38.557Z\",\"caller\":\"etcdserver/corrupt.go:244\",\"msg\":\"finished peer corruption check\",\"number-of-peers-checked\":0}\r\n```\r\n\r\nLooking at a follower, we see the requested revision has been compacted\r\n\r\n```\r\n{\"level\":\"warn\",\"ts\":\"2022-08-02T17:48:38.516Z\",\"caller\":\"etcdserver/corrupt.go:377\",\"msg\":\"failed to get hashKV\",\"requested-revision\":2592,\"error\":\"mvcc: required revision has been compacted\"}\r\n```\r\n\r\nI then wrote a key to etcd and observed the corruption check working correctly on the next run.\n\n### What did you expect to happen?\n\nThe corruption check should work regardless of whether or not a compaction has happened very recently.\n\n### How can we reproduce it (as minimally and precisely as possible)?\n\n- Set `--experimental-corrupt-check-time` to something very short like 1m\r\n- Compact your etcd cluster\r\n- Note that the next corruption check doesn't work\r\n- Insert a key into etcd\r\n- Note that the next corruption check does work\n\n### Anything else we need to know?\n\n_No response_\n\n### Etcd version (please run commands below)\n\n
\r\n\r\n```console\r\n$ etcd --version\r\netcd Version: 3.5.3\r\nGit SHA: GitNotFound\r\nGo Version: go1.16.2\r\nGo OS/Arch: linux/amd64\r\n\r\n$ etcdctl version\r\netcdctl version: 3.5.3\r\nAPI version: 3.5\r\n```\r\n\r\n
\r\n\n\n### Etcd configuration (command line flags or environment variables)\n\n
\r\n ...\r\n --enable-v2=false\r\n --auto-compaction-retention=1h\r\n --experimental-corrupt-check-time=6h\r\n --experimental-initial-corrupt-check\r\n --log-level 'info'\r\n ...\r\n
\r\n\n\n### Etcd debug information (please run commands blow, feel free to obfuscate the IP address or FQDN in the output)\n\n
\r\n\r\nLeaving these off. Happy to share more details if required. It is a healthy five node cluster, no learners, all running v3.5.3.\r\n\r\n```console\r\n$ etcdctl member list -w table\r\n# paste output here\r\n\r\n$ etcdctl --endpoints= endpoint status -w table\r\n# paste output here\r\n```\r\n\r\n
\r\n\n\n### Relevant log output\n\n_No response_\n", "branch": "v3.5.3", "issue_url": "https://github.com/etcd-io/etcd/issues/14325", "fix_url": "https://github.com/etcd-io/etcd/pull/14457", "issue_created": "2022-08-09", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "etcd-14382", "system": "etcd", "issue_number": "14382", "lite": false, "title": "ETCD fails to start after performing alarm list operation and then power off/on", "description": "### What happened?\r\n\r\nWith a cluster of three nodes setup using https://github.com/bitnami/charts/blob/master/bitnami/etcd/README.md it was noticed that the ETCD nodes failed to start after a forced reboot of the underlying worker nodes. A graceful shutdown will not result in this issue.\r\n\r\nThe logs indicated a mismatch in the raft log index between the v2 *.snap files and the v3 db file where the index of the snap files was higher than that of the v3 db file causing ETCD to look for a snap.db file that did not exist (see logs).\r\n\r\nThe index of the snap file was derived from the file name (eg. `0000000000000017-0000000000124f8c.snap`) while the consistent_index of the v3 db was extracted using bbolt, `bbolt get db meta consistent_index | hexdump` => `0xb4903`.\r\n\r\nSo far the issue looked very much like what is described in #11949. The \"fix\" described in that issue to get the cluster up and running again also worked, to remove/move the `*.snap` files.\r\n\r\nWorth mentioning: This cluster had not had any writes to it for serveral weeks ahead of the reboot. The data in it is mostly read. Doing a proper write to the cluster will set the consistent_index of the v3 DB to an up-to-date value of the raft index.\r\n\r\nAfter some investigation into why this index difference the between the snapshots and the v3 store occurred it was found that the health check executed regularly by Kubernetes was the reason for the version drift.\r\n\r\nThe health and readiness check regularly executes `etcdctl endpoint health` to determine if the cluster is healthy or not. In ETCD 3.4 this was a simple GET on the health key but since https://github.com/etcd-io/etcd/pull/12150 it also includes checking the alarm list to verify that it is empty. For some reason listing the alarms also triggers a write/apply (see attached logs). And for some reason this apply is only applied to the V2 store, not the V3 store. This cause the index in the V2 store to drift from the V3 store until a proper write is performed. I have not dug into the reason for why the write is performed and why it is missing from the V3 store.\r\n\r\nThe behaviour is only present in this form in 3.5 since the health check in 3.4 does not include listing the alarms.\r\n\r\nThe problem is easy to reproduce locally. See description.\r\n\r\n### What did you expect to happen?\r\n\r\nI would always expect ETCD to be able to start properly regardless of how the shutdown was done.\r\n\r\n### How can we reproduce it (as minimally and precisely as possible)?\r\n\r\nLocally:\r\n```sh\r\n# Use very low snapshot count to more quickly trigger the issue\r\n$ ./etcd --snapshot-count=5 --log-level=debug\r\n\r\n# In a different terminal, repeat six times to trigger creation of a snapshot file (you'll see a `triggering snapshot` log message in the server log when this happens)\r\n$ ./etcdctl endpoint health\r\n$ ./etcdctl endpoint health\r\n$ ./etcdctl endpoint health\r\n$ ./etcdctl endpoint health\r\n$ ./etcdctl endpoint health\r\n$ ./etcdctl endpoint health\r\n\r\n# Kill etcd server process\r\n$ kill -9 \r\n\r\n# Try to start ETCD again, this will fail with the attached log message\r\n$ ./etcd --snapshot-count=5 --log-level=debug\r\n```\r\n\r\n### Anything else we need to know?\r\n\r\n_No response_\r\n\r\n### Etcd version (please run commands below)\r\n\r\n
\r\n\r\n```console\r\n$ etcd --version\r\netcd Version: 3.5.4\r\nGit SHA: 08407ff76\r\nGo Version: go1.16.15\r\nGo OS/Arch: darwin/amd64\r\n\r\n$ etcdctl version\r\netcdctl version: 3.5.4\r\nAPI version: 3.5\r\n```\r\n\r\n
\r\n\r\n\r\n### Etcd configuration (command line flags or environment variables)\r\n\r\n
\r\n\r\nSee steps to reproduce\r\n\r\n
\r\n\r\n\r\n### Etcd debug information (please run commands blow, feel free to obfuscate the IP address or FQDN in the output)\r\n\r\n
\r\n\r\n```console\r\nSee steps to reproduce\r\n```\r\n\r\n
\r\n\r\n\r\n### Relevant log output\r\n\r\n```shell\r\n# Log printed upon startup failure\r\n{\"level\":\"info\",\"ts\":\"2022-07-23T18:21:35.360Z\",\"caller\":\"etcdserver/backend.go:81\",\"msg\":\"opened backend db\",\"path\":\"/bitnami/etcd/data/member/snap/db\",\"took\":\"174.548µs\"}\r\n{\"level\":\"info\",\"ts\":\"2022-07-23T18:21:36.259Z\",\"caller\":\"etcdserver/server.go:508\",\"msg\":\"recovered v2 store from snapshot\",\"snapshot-index\":1200012,\"snapshot-size\":\"25 kB\"}\r\n{\"level\":\"warn\",\"ts\":\"2022-07-23T18:21:36.260Z\",\"caller\":\"snap/db.go:88\",\"msg\":\"failed to find [SNAPSHOT-INDEX].snap.db\",\"snapshot-index\":1200012,\"snapshot-file-path\":\"/bitnami/etcd/data/member/snap/0000000000124f8c.snap.db\",\"error\":\"snap: snapshot file doesn't exist\"}\r\n{\"level\":\"panic\",\"ts\":\"2022-07-23T18:21:36.261Z\",\"caller\":\"etcdserver/server.go:515\",\"msg\":\"failed to recover v3 backend from snapshot\",\"error\":\"failed to find database snapshot file (snap: snapshot file doesn't exist)\",\"stacktrace\":\"go.etcd.io/etcd/server/v3/etcdserver.NewServer\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/server.go:515\\ngo.etcd.io/etcd/server/v3/embed.StartEtcd\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/embed/etcd.go:245\\ngo.etcd.io/etcd/server/v3/etcdmain.startEtcd\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdmain/etcd.go:228\\ngo.etcd.io/etcd/server/v3/etcdmain.startEtcdOrProxyV2\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdmain/etcd.go:123\\ngo.etcd.io/etcd/server/v3/etcdmain.Main\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/etcdmain/main.go:40\\nmain.main\\n\\t/go/src/go.etcd.io/etcd/release/etcd/server/main.go:32\\nruntime.main\\n\\t/go/gos/go1.16.15/src/runtime/proc.go:225\"}\r\npanic: failed to recover v3 backend from snapshot\r\ngoroutine 1 [running]:\r\ngo.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc000506300, 0xc000532f40, 0x1, 0x1)\r\n/go/pkg/mod/go.uber.org/zap@v1.17.0/zapcore/entry.go:234 +0x58d\r\ngo.uber.org/zap.(*Logger).Panic(0xc000010fa0, 0x1234726, 0x2a, 0xc000532f40, 0x1, 0x1)\r\n/go/pkg/mod/go.uber.org/zap@v1.17.0/logger.go:227 +0x85\r\ngo.etcd.io/etcd/server/v3/etcdserver.NewServer(0xc0000460ca, 0xd, 0x0, 0x0, 0x0, 0x0, 0xc0005150e0, 0x2, 0x2, 0xc00053c480, ...)\r\n/go/src/go.etcd.io/etcd/release/etcd/server/etcdserver/server.go:515 +0x1656\r\ngo.etcd.io/etcd/server/v3/embed.StartEtcd(0xc000104000, 0xc000104600, 0x0, 0x0)\r\n/go/src/go.etcd.io/etcd/release/etcd/server/embed/etcd.go:245 +0xef8\r\ngo.etcd.io/etcd/server/v3/etcdmain.startEtcd(0xc000104000, 0x12089be, 0x6, 0xc0004b7201, 0x2)\r\n/go/src/go.etcd.io/etcd/release/etcd/server/etcdmain/etcd.go:228 +0x32\r\ngo.etcd.io/etcd/server/v3/etcdmain.startEtcdOrProxyV2(0xc00003a1f0, 0x1, 0x1)\r\n/go/src/go.etcd.io/etcd/release/etcd/server/etcdmain/etcd.go:123 +0x257a\r\ngo.etcd.io/etcd/server/v3/etcdmain.Main(0xc00003a1f0, 0x1, 0x1)\r\n/go/src/go.etcd.io/etcd/release/etcd/server/etcdmain/main.go:40 +0x13f\r\n\r\n\r\n# Server debug logs when running `etcdctl endpoint health`\r\n{\"level\":\"debug\",\"ts\":\"2022-08-25T15:21:32.425+0200\",\"caller\":\"v3rpc/interceptor.go:182\",\"msg\":\"request stats\",\"start time\":\"2022-08-25T15:21:32.425+0200\",\"time spent\":\"114.504µs\",\"remote\":\"127.0.0.1:51728\",\"response type\":\"/etcdserverpb.KV/Range\",\"request count\":0,\"request size\":8,\"response count\":0,\"response size\":28,\"request content\":\"key:\\\"health\\\" \"}\r\n{\"level\":\"debug\",\"ts\":\"2022-08-25T15:21:32.426+0200\",\"caller\":\"etcdserver/server.go:2122\",\"msg\":\"Applying entries\",\"num-entries\":1}\r\n{\"level\":\"debug\",\"ts\":\"2022-08-25T15:21:32.426+0200\",\"caller\":\"etcdserver/server.go:2125\",\"msg\":\"Applying entry\",\"index\":70,\"term\":5,\"type\":\"EntryNormal\"}\r\n{\"level\":\"debug\",\"ts\":\"2022-08-25T15:21:32.426+0200\",\"caller\":\"etcdserver/server.go:2184\",\"msg\":\"apply entry normal\",\"consistent-index\":60,\"entry-index\":70,\"should-applyV3\":true}\r\n{\"level\":\"debug\",\"ts\":\"2022-08-25T15:21:32.426+0200\",\"caller\":\"etcdserver/server.go:2211\",\"msg\":\"applyEntryNormal\",\"raftReq\":\"header: alarm:<> \"}\r\n{\"level\":\"debug\",\"ts\":\"2022-08-25T15:21:32.426+0200\",\"caller\":\"v3rpc/interceptor.go:182\",\"msg\":\"request stats\",\"start time\":\"2022-08-25T15:21:32.426+0200\",\"time spent\":\"241.967µs\",\"remote\":\"127.0.0.1:51728\",\"response type\":\"/etcdserverpb.Maintenance/Alarm\",\"request count\":-1,\"request size\":-1,\"response count\":-1,\"response size\":-1,\"request content\":\"\"}\r\n{\"level\":\"info\",\"ts\":\"2022-08-25T15:21:32.428+0200\",\"caller\":\"zapgrpc/zapgrpc.go:174\",\"msg\":\"[transport] transport: loopyWriter.run returning. connection error: desc = \\\"transport is closing\\\"\"}\r\n```\r\n\n", "branch": "v3.5.4", "issue_url": "https://github.com/etcd-io/etcd/issues/14382", "fix_url": "https://github.com/etcd-io/etcd/pull/14419", "issue_created": "2022-08-25", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "etcd-14571", "system": "etcd", "issue_number": "14571", "lite": false, "title": "3.5.5: client auth failures on new member first startup", "description": "After cluster upgrade from 3.5.4 to 3.5.5 we are seeing auth issues on new nodes after first startup. Cluster runs in auth-enable mode. New node joins the cluster, fetches the snapshot, but fails all client requests ", "branch": "v3.5.5", "issue_url": "https://github.com/etcd-io/etcd/issues/14571", "fix_url": "https://github.com/etcd-io/etcd/pull/14574", "issue_created": "2022-10-11", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "etcd-14764", "system": "etcd", "issue_number": "14764", "lite": false, "title": "Manipulating Keys and Manipulating Users Concurrency Causes Segmentation Violation in Client", "description": "### What happened?\r\n\r\nI created a bunch of keys concurrently with goroutines. I created a bunch of users concurrency with goroutines in a separate process.\r\n\r\nThe process generating the keys aborted with this:\r\n```\r\n{\"level\":\"warn\",\"ts\":\"2022-11-15T08:33:12.382-0500\",\"logger\":\"etcd-client\",\"caller\":\"v3@v3.5.5/retry_interceptor.go:62\",\"msg\":\"retrying of unary invoker failed\",\"target\":\"etcd-endpoints://0xc000215340/127.0.0.1:32379\",\"attempt\":0,\"error\":\"rpc error: code = InvalidArgument desc = etcdserver: revision of auth store is old\"}\r\npanic: runtime error: invalid memory address or nil pointer dereference\r\n[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x95a390]\r\n\r\ngoroutine 29 [running]:\r\ngo.etcd.io/etcd/client/v3.(*Client).unaryClientInterceptor.func1({0xb7ee68?, 0xc000122000?}, {0xaa0935, 0x14}, {0xa79540, 0xc0002ff1a0}, {0xa6f500, 0xc000376e70}, 0xc000266700, 0xadf000, ...)\r\n\t/home/eric/go/pkg/mod/go.etcd.io/etcd/client/v3@v3.5.5/retry_interceptor.go:81 +0x7f0\r\ngoogle.golang.org/grpc.(*ClientConn).Invoke(0xc000078a98?, {0xb7ee68?, 0xc000122000?}, {0xaa0935?, 0x8?}, {0xa79540?, 0xc0002ff1a0?}, {0xa6f500?, 0xc000376e70?}, {0xf69120, ...})\r\n\t/home/eric/go/pkg/mod/google.golang.org/grpc@v1.41.0/call.go:35 +0x21f\r\ngo.etcd.io/etcd/api/v3/etcdserverpb.(*kVClient).Put(0xc000139230, {0xb7ee68, 0xc000122000}, 0x40f107?, {0xf69120, 0x3, 0x3})\r\n\t/home/eric/go/pkg/mod/go.etcd.io/etcd/api/v3@v3.5.5/etcdserverpb/rpc.pb.go:6469 +0xc9\r\ngo.etcd.io/etcd/client/v3.(*retryKVClient).Put(0xc000123bf0?, {0xb7ee68?, 0xc000122000?}, 0xc000078b38?, {0xf69120?, 0x8?, 0x0?})\r\n\t/home/eric/go/pkg/mod/go.etcd.io/etcd/client/v3@v3.5.5/retry.go:109 +0x30\r\ngo.etcd.io/etcd/client/v3.(*kv).Do(_, {_, _}, {0x2, {0xc000123be0, 0xa, 0x10}, {0x0, 0x0, 0x0}, ...})\r\n\t/home/eric/go/pkg/mod/go.etcd.io/etcd/client/v3@v3.5.5/kv.go:156 +0x2f8\r\ngo.etcd.io/etcd/client/v3.(*kv).Put(0x1?, {0xb7ee68, 0xc000122000}, {0xc000123bd0?, 0x0?}, {0xa961c5?, 0x0?}, {0x0, 0x0, 0x0})\r\n\t/home/eric/go/pkg/mod/go.etcd.io/etcd/client/v3@v3.5.5/kv.go:114 +0xd3\r\nmain.churnKeys.func1()\r\n\t/home/eric/Projects/test/etcd-bug/main.go:61 +0x15c\r\ncreated by main.churnKeys\r\n\t/home/eric/Projects/test/etcd-bug/main.go:57 +0x53\r\n```\r\n\r\n### What did you expect to happen?\r\n\r\nIdeally, I expected the client manipulating the keys (root user not impacted by the user manipulations) to handle the user changes gracefully.\r\n\r\nHowever, I would have settled for getting an error in the `*clientv3.Client.Put` call return value without the panic.\r\n\r\n### How can we reproduce it (as minimally and precisely as possible)?\r\n\r\n1. Run etcd on a local kubernetes with the following terraform scripts: https://github.com/Ferlab-Ste-Justine/terraform-provider-etcd/tree/main/test-environment/server\r\n\r\nCommands to launch etcd (assumes you have a localhost kubernetes not running in a vm):\r\n```\r\nterraform apply\r\n```\r\n2. In a separate directory paste the following code in main.go:\r\n```\r\npackage main\r\n\r\nimport (\r\n\t\"context\"\r\n\t\"crypto/tls\"\r\n\t\"crypto/x509\"\r\n\t\"errors\"\r\n\t\"fmt\"\r\n\t\"io/ioutil\"\r\n\t\"os\"\r\n\t\"sync\"\r\n\t\"sync/atomic\"\r\n\r\n\tclientv3 \"go.etcd.io/etcd/client/v3\"\r\n)\r\n\r\nfunc connect() (*clientv3.Client, error) {\r\n\ttlsConf := &tls.Config{}\r\n\r\n\t//User Cert\r\n\tcertData, err := tls.LoadX509KeyPair(\"./certs/root.pem\", \"./certs/root.key\")\r\n\tif err != nil {\r\n\t\treturn nil, errors.New(fmt.Sprintf(\"Failed to load user credentials: %s\", err.Error()))\r\n\t}\r\n\t(*tlsConf).Certificates = []tls.Certificate{certData}\r\n\r\n\t//Ca Cert\r\n\tcaCertContent, err := ioutil.ReadFile(\"./certs/ca.pem\")\r\n\tif err != nil {\r\n\t\treturn nil, errors.New(fmt.Sprintf(\"Failed to read root certificate file: %s\", err.Error()))\r\n\t}\r\n\troots := x509.NewCertPool()\r\n\tok := roots.AppendCertsFromPEM(caCertContent)\r\n\tif !ok {\r\n\t\treturn nil, errors.New(\"Failed to parse root certificate authority\")\r\n\t}\r\n\t(*tlsConf).RootCAs = roots\r\n\r\n\t//Connection\r\n\tcli, connErr := clientv3.New(clientv3.Config{\r\n\t\tEndpoints: []string{\"127.0.0.1:32379\"},\r\n\t\tTLS: tlsConf,\r\n\t})\r\n\tif connErr != nil {\r\n\t\treturn nil, errors.New(fmt.Sprintf(\"Failed to connect to etcd servers: %s\", connErr.Error()))\r\n\t}\r\n\r\n\treturn cli, nil\r\n}\r\n\r\nfunc churnKeys(cli *clientv3.Client, cycles int64, paralellism int) {\r\n\tvar wg sync.WaitGroup\r\n\tcounter := int64(0)\r\n\r\n\tfor i := 0; i < paralellism; i++ {\r\n\t\twg.Add(1)\r\n\t\tgo func() {\r\n\t\t\tdefer wg.Done()\r\n\t\t\tfor counter < cycles {\r\n\t\t\t\tidx := atomic.AddInt64(&counter, 1)\r\n\t\t\t\t_, putErr := cli.Put(context.Background(), fmt.Sprintf(\"test-key-%d\", idx), \"test\")\r\n\t\t\t\tif putErr != nil {\r\n\t\t\t\t\tfmt.Println(putErr)\r\n\t\t\t\t\tcontinue\r\n\t\t\t\t}\r\n\r\n\t\t\t\t_, delErr := cli.Delete(context.Background(), fmt.Sprintf(\"test-key-%d\", idx))\r\n\t\t\t\tif delErr != nil {\r\n\t\t\t\t\tfmt.Println(putErr)\r\n\t\t\t\t\tcontinue\r\n\t\t\t\t}\t\t\t\r\n\t\t\t}\t\r\n\t\t}()\r\n\t}\r\n\r\n\twg.Wait()\r\n}\r\n\r\nfunc churnUsers(cli *clientv3.Client, cycles int64, paralellism int) {\r\n\tvar wg sync.WaitGroup\r\n\tcounter := int64(0)\r\n\r\n\tfor i := 0; i < paralellism; i++ {\r\n\t\twg.Add(1)\r\n\t\tgo func() {\r\n\t\t\tdefer wg.Done()\r\n\t\t\tfor counter < cycles {\r\n\t\t\t\tidx := atomic.AddInt64(&counter, 1)\r\n\r\n\t\t\t\t_, addErr := cli.UserAdd(context.Background(), fmt.Sprintf(\"test-user-%d\", idx), \"test\")\r\n\t\t\t\tif addErr != nil {\r\n\t\t\t\t\tfmt.Println(addErr)\r\n\t\t\t\t\tcontinue\r\n\t\t\t\t}\r\n\r\n\t\t\t\t_, delErr := cli.UserDelete(context.Background(), fmt.Sprintf(\"test-user-%d\", idx))\r\n\t\t\t\tif delErr != nil {\r\n\t\t\t\t\tfmt.Println(delErr)\r\n\t\t\t\t\tcontinue\r\n\t\t\t\t}\r\n\t\t\t}\r\n\t\t}()\r\n\t}\r\n\r\n\twg.Wait()\r\n}\r\n\r\nfunc main() {\r\n\tcli, connErr := connect()\r\n\tif connErr != nil {\r\n\t\tfmt.Println(connErr)\r\n\t\tos.Exit(1)\r\n\t}\r\n\r\n\t//churnKeys(cli, 1000, 10)\r\n\t//churnUsers(cli, 1000, 10)\r\n}\r\n```\r\n3. Copy the generated \"certs\" from your terraform scripts with the main.go file and run:\r\n\r\n```\r\ngo mod init etcd-bug\r\ngo mod tidy\r\n```\r\n\r\n4. Uncomment the `churnKeys(cli, 1000, 10)` line and run:\r\n```\r\ngo build .\r\nmv etcd-bug etcd-bug-keys\r\n```\r\n\r\n5. Comment the `churnKeys(cli, 1000, 10)` line, uncomment the `churnUsers(cli, 1000, 10)` line and run:\r\n```\r\ngo build .\r\nmv etcd-bug etcd-bug-users\r\n```\r\n\r\n6. In two separate shells: Run etcd-bug-users and before it finishes, run etcd-bug-keys in the other shell. The etcd-bug-keys process will panic with the above error.\r\n\r\n### Anything else we need to know?\r\n\r\nInterestingly, when the server was running 3.4, the client only produced a user error without the panic and segmentation violation. That started occurring once I switched the etcd server to 3.5.\r\n\r\n### Etcd version (please run commands below)\r\n\r\n
\r\n\r\n```console\r\n# etcd --version\r\netcd Version: 3.5.5\r\nGit SHA: 19002cfc6\r\nGo Version: go1.16.15\r\nGo OS/Arch: linux/amd64\r\n```\r\n\r\n
\r\n\r\n\r\n### Etcd configuration (command line flags or environment variables)\r\n\r\n
\r\n\r\n# paste your configuration here\r\n\r\n
\r\n\r\n\r\n### Etcd debug information (please run commands blow, feel free to obfuscate the IP address or FQDN in the output)\r\n\r\n
\r\n\r\n```console\r\n$ etcdctl member list -w table\r\n# paste output here\r\n\r\n$ etcdctl --endpoints= endpoint status -w table\r\n# paste output here\r\n```\r\n\r\n
\r\n\r\n\r\n### Relevant log output\r\n\r\n_No response_\n", "branch": "v3.5.5", "issue_url": "https://github.com/etcd-io/etcd/issues/14764", "fix_url": "https://github.com/etcd-io/etcd/pull/14770", "issue_created": "2022-11-15", "severity": "Critical", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "etcd-15247", "system": "etcd", "issue_number": "15247", "lite": false, "title": "All leases are revoked when the etcd leader is stuck in handling raft Ready due to slow fdatasync or high CPU", "description": "We have 3 etcd nodes which are running on k8s, the etcd pod use portworx storage for db saving, we've found when rebooting the portworx node, it will cause etcd to be stuck in fdatasync, if this etcd node is leader, then it will cause below 2 lease keep alive issues. 1, the old leader still revokes lease after it steped to follower. 2, the old leader still handle lease keep alive request from the connected client.", "branch": "v3.4.3", "issue_url": "https://github.com/etcd-io/etcd/issues/15247", "fix_url": "https://github.com/etcd-io/etcd/pull/16822", "issue_created": "2023-02-06", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "etcd-17507", "system": "etcd", "issue_number": "17507", "lite": true, "title": "Etcd not respond to progress notification on newly created watch RPC until there is a event in a watch", "description": "If the watch is newly created and not yet synced, and the client sends a progress request during that window, etcd may mark progress as deferred and then never send the progress response unless an actual watch event later occurs. If no events match the watch filter, the client can wait forever for progress notifications.", "branch": "v3.5.10", "issue_url": "https://github.com/etcd-io/etcd/issues/17507", "fix_url": "https://github.com/etcd-io/etcd/pull/17557", "issue_created": "2024-02-28", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hbase-28376", "system": "hbase", "issue_number": "28376", "lite": true, "title": "", "description": "Master Failed to Start after upgrading from 2.5.10 to 3.0.0-beta-1\n\n2024-12-01T19:00:47,390 ERROR [master/master:16000:becomeActiveMaster] master.HMaster: Failed to become active master\njava.lang.IllegalStateException: Expected the service ClusterSchemaServiceImpl [FAILED] to be RUNNING, but the service has FAILED\n at org.apache.hbase.thirdparty.com.google.common.util.concurrent.AbstractService.checkCurrentState(AbstractService.java:384) ~[hbase-shaded-miscellaneous-4.1.5.jar:4.1.5]\n at org.apache.hbase.thirdparty.com.google.common.util.concurrent.AbstractService.awaitRunning(AbstractService.java:324) ~[hbase-shaded-miscellaneous-4.1.5.jar:4.1.5]\n at org.apache.hadoop.hbase.master.HMaster.initClusterSchemaService(HMaster.java:1535) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:1204) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2494) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:613) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.trace.TraceUtil.lambda$tracedRunnable$2(TraceUtil.java:155) ~[hbase-common-3.0.0-beta-1.jar:3.0.0-beta-1]\n at java.lang.Thread.run(Thread.java:840) ~[?:?]\nCaused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 18 actions: RetriesExhaustedException: 18 times, servers with issues:\n at org.apache.hadoop.hbase.client.BufferedMutatorOverAsyncBufferedMutator.makeError(BufferedMutatorOverAsyncBufferedMutator.java:107) ~[hbase-client-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.client.BufferedMutatorOverAsyncBufferedMutator.internalFlush(BufferedMutatorOverAsyncBufferedMutator.java:122) ~[hbase-client-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.client.BufferedMutatorOverAsyncBufferedMutator.close(BufferedMutatorOverAsyncBufferedMutator.java:166) ~[hbase-client-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.master.TableNamespaceManager.migrateNamespaceTable(TableNamespaceManager.java:92) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:122) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.master.ClusterSchemaServiceImpl.doStart(ClusterSchemaServiceImpl.java:61) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hbase.thirdparty.com.google.common.util.concurrent.AbstractService.startAsync(AbstractService.java:252) ~[hbase-shaded-miscellaneous-4.1.5.jar:4.1.5]\n at org.apache.hadoop.hbase.master.HMaster.initClusterSchemaService(HMaster.java:1532) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n ... 5 more\n2024-12-01T19:00:47,390 ERROR [master/master:16000:becomeActiveMaster] master.HMaster: Master server abort: loaded coprocessors are: []\n2024-12-01T19:00:47,390 ERROR [master/master:16000:becomeActiveMaster] master.HMaster: ***** ABORTING master master,16000,1733059831148: Unhandled exception. Starting shutdown. *****\njava.lang.IllegalStateException: Expected the service ClusterSchemaServiceImpl [FAILED] to be RUNNING, but the service has FAILED\n at org.apache.hbase.thirdparty.com.google.common.util.concurrent.AbstractService.checkCurrentState(AbstractService.java:384) ~[hbase-shaded-miscellaneous-4.1.5.jar:4.1.5]\n at org.apache.hbase.thirdparty.com.google.common.util.concurrent.AbstractService.awaitRunning(AbstractService.java:324) ~[hbase-shaded-miscellaneous-4.1.5.jar:4.1.5]\n at org.apache.hadoop.hbase.master.HMaster.initClusterSchemaService(HMaster.java:1535) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:1204) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2494) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:613) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.trace.TraceUtil.lambda$tracedRunnable$2(TraceUtil.java:155) ~[hbase-common-3.0.0-beta-1.jar:3.0.0-beta-1]\n at java.lang.Thread.run(Thread.java:840) ~[?:?]\nRegion Server has below warning log\n\n \n\n2024-12-01T19:00:47,354 WARN [RpcServer.priority.RWQ.Fifo.write.handler=0,queue=0,port=16020] regionserver.HRegion: No such column family in batch mutation in region org.apache.hadoop.hbase.regionserver.HRegion$MutationBatchOperation@74bf756d\norg.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException: Column family ns does not exist in region hbase:meta,,1.1588230740 in table 'hbase:meta', {TABLE_ATTRIBUTES => {IS_META => 'true', coprocessor$1 => '|org.apache.hadoop.hbase.coprocessor.MultiRowMutationEndpoint|536870911|', METADATA => {'hbase.store.file-tracker.impl' => 'DEFAULT'}}}, {NAME => 'info', INDEX_BLOCK_ENCODING => 'NONE', VERSIONS => '3', KEEP_DELETED_CELLS => 'FALSE', DATA_BLOCK_ENCODING => 'ROW_INDEX_V1', TTL => 'FOREVER', MIN_VERSIONS => '0', REPLICATION_SCOPE => '0', BLOOMFILTER => 'ROWCOL', IN_MEMORY => 'true', COMPRESSION => 'NONE', BLOCKCACHE => 'true', BLOCKSIZE => '8192 B (8KB)'}, {NAME => 'rep_barrier', INDEX_BLOCK_ENCODING => 'NONE', VERSIONS => '2147483647', KEEP_DELETED_CELLS => 'FALSE', DATA_BLOCK_ENCODING => 'ROW_INDEX_V1', TTL => 'FOREVER', MIN_VERSIONS => '0', REPLICATION_SCOPE => '0', BLOOMFILTER => 'ROWCOL', IN_MEMORY => 'true', COMPRESSION => 'NONE', BLOCKCACHE => 'true', BLOCKSIZE => '65536 B (64KB)'}, {NAME => 'table', INDEX_BLOCK_ENCODING => 'NONE', VERSIONS => '3', KEEP_DELETED_CELLS => 'FALSE', DATA_BLOCK_ENCODING => 'ROW_INDEX_V1', TTL => 'FOREVER', MIN_VERSIONS => '0', REPLICATION_SCOPE => '0', BLOOMFILTER => 'ROWCOL', IN_MEMORY => 'true', COMPRESSION => 'NONE', BLOCKCACHE => 'true', BLOCKSIZE => '8192 B (8KB)'}\n at org.apache.hadoop.hbase.regionserver.HRegion.checkFamily(HRegion.java:5344) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion.checkFamily(HRegion.java:5331) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion.checkFamilies(HRegion.java:5325) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion.access$100(HRegion.java:239) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion$MutationBatchOperation.checkAndPreparePut(HRegion.java:3849) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion$BatchOperation.checkAndPrepareMutation(HRegion.java:3486) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion$BatchOperation.checkAndPrepareMutation(HRegion.java:3498) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion$MutationBatchOperation$1.visit(HRegion.java:3878) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion$BatchOperation.visitBatchOperations(HRegion.java:3377) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion$MutationBatchOperation.checkAndPrepare(HRegion.java:3857) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:4753) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:4673) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:984) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:902) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:867) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2830) ~[hbase-server-3.0.0-beta-1.jar:3.0.0-beta-1]\n at org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45018) ~[hbase-protocol-shaded-3.0.0-beta-1.jar:3.0.0-beta-1]\ncomplete log files are attached", "branch": "2306820df8b41d9af5227465ee2cf9e18b8f0b5c", "issue_url": "https://issues.apache.org/jira/browse/HBASE-28376", "fix_url": null, "issue_created": "2024-02-17", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": false, "contains_analysis": false, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hbase-28830", "system": "hbase", "issue_number": "28830", "lite": false, "title": "", "description": "when a procedure on a table executed as a child procedure, furthur table procedure operations on that table are blocked forever waiting to aquire the table procedure lock .\n\nThis issue occur due to not clearing of table lock for the table procedures submitted as child procedures after the changes in HBASE-28683,", "branch": "rel/3.0.0-beta-1", "issue_url": "https://issues.apache.org/jira/browse/HBASE-28830", "fix_url": null, "issue_created": "2024-09-10", "severity": "Critical", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": false, "contains_analysis": true, "analysis_removed": "Partly Removed", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hbase-28962", "system": "hbase", "issue_number": "28962", "lite": true, "title": "", "description": "Meta replication is inconsistent after startup when reusing HBase storage location for example the new cluster is created with the same S3 storage location that a previous one had. \nUSE_META_REPLICAS is set to true\nMETA_REPLICAS_NUM is set to 3\nFor both\nhbck output:\n\nERROR: hbase:meta, replicaId 1 is not found on any region.\nERROR: hbase:meta, replicaId 2 is not found on any region.\nERROR: hbase:meta table is not consistent. Run HBCK with proper fix options to fix hbase:meta inconsistency. Exiting...\nSummary:\n3 inconsistencies detected.\nStatus: INCONSISTENT", "branch": "db3ba44a4c692d26e70b6030fc519e92fd79f638", "issue_url": "https://issues.apache.org/jira/browse/HBASE-28962", "fix_url": null, "issue_created": "2024-11-06", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": null, "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hbase-29021", "system": "hbase", "issue_number": "29021", "lite": false, "title": "", "description": "Symptoms\nAfter upgrading from HBase 2.5.10 to HBase 2.6.1, I observed an inconsistent read across versions.\n\nBefore the upgrade, I created a table with one row. Invoking a count command returns 1. After upgrading to 2.6.1, execute the same count command, it returns 0.\n\ncount 'test'\n\nOld Version Result:\n1 row(s)\nTook 0.5582 seconds\n=> 1\n\nNew Version Result: \n0 row(s)\nTook 1.4439 seconds\n=> 0 \nReproduce\nIt can be reproduced deterministically with the following steps\n\nStep1: Start up the HBase cluster in 2.5.10 and execute the following commands\n\ncreate 'test', 'cf', CONFIGURATION => {'hbase.store.file-tracker.impl' => 'FILE'}\nput 'test', 'row', 'cf:q', 'value'\nStep2: Execute the count command in the old version\n\ncount 'test'\n\n1 row(s)\nTook 0.5582 seconds\n=> 1 \nStep3: Stop the entire cluster, upgrade to 2.6.1 and execute the same count command\n\ncount 'test'\n\n0 row(s)\nTook 0.0842 seconds\n=> 0\nAnalysis\nThe names of StoreFileListFile differ between the two versions:\n\nIn 2.5.10: f1 or f2\nIn 2.6.1: f1.{timestamp} or f2.{timestamp}\nThe addition of a timestamp to the file name was introduced in HBASE-26791.\n\nIt can be resolved by handling missing timestamps by setting them to 0.\n\nHowever, in the case of downgrading versions, the above approach does not work. A workaround is available:\n\nChange the storefile tracker implementation from FILE > MIGRATION > DEFAULT before downgrading.", "branch": "rel/2.6.1", "issue_url": "https://issues.apache.org/jira/browse/HBASE-29021", "fix_url": null, "issue_created": "2024-12-06", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": false, "contains_analysis": true, "analysis_removed": "Partly Removed", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hbase-29108", "system": "hbase", "issue_number": "29108", "lite": true, "title": "", "description": "Background:\n\nWhen hbase performs a compaction, it writes the compaction result (1 or more storefiles) to a file in HDFS under /hbase/data////.tmp//\nOnce the compaction succeeds, the storefile is renamed to /hbase/data//
/// (moved out of the .tmp directory to where storefiles should be stored and are read to serve client RPC's)\nWhen compaction fails, in some cases cleanup is performed and the storefile under .tmp directory is cleaned up (deleted). However, in other cases the storefile is left to be under .tmp directory (e.g. when one of the datanodes where the storefile's last block was being written gets SIGKILL'ed)\nProblem\n\nIn certain cases, a storefile under .tmp will contain 2 corrupt block replica and 1 good block replica (e.g. two replicas can be corrupt due to reason GENSTAMP_MISMATCH - generation stamp differs AND/OR have a file length lower than the good replica's file lengths). Namenode will detect this block corruption and report it in its metrics\nThe corrupt blocks will remain corrupt and the good block replica will not be re-replicated to other datanodes to fix the corruption.\nThe storefile under .tmp remains \"open\" / under-construction by the regionserver.\nImpact\n\nNo visible impact on hbase clients (storefiles under .tmp are not read to return data to clients).\nThis can trip up alerts & monitoring (there are corrupt blocks being reported by namenode that do not fix themselves until regions are reopened/regionservers restart)\nDecommissioning of datanodes can get blocked indefinitely (a block that contains a corrupt replica but is part of a file that is still open does not get re-replicated to other datanodes even if a good replica is available, thus the datanode that has the only good replica of a block cannot be decommissioned)\nWorkaround\n\nA region can be re-opened (e.g. by restarting a regionserver on which the region is open), which causes the region's .tmp directory to be deleted recursively once the region is opened again, removing all corrupt blocks and leftover storefiles.", "branch": "rel/2.5.10", "issue_url": "https://issues.apache.org/jira/browse/HBASE-29108", "fix_url": null, "issue_created": "2025-02-01", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hdfs-10512", "system": "hdfs", "issue_number": "10512", "lite": true, "title": "VolumeScanner may terminate due to NPE in DataNode.reportBadBlocks", "description": "VolumeScanner may terminate due to unexpected NullPointerException thrown in DataNode.reportBadBlocks(). This is different from HDFS-8850/HDFS-9190\nI observed this bug in a production CDH 5.5.1 cluster and the same bug still persist in upstream trunk.\n2016-04-07 20:30:53,830 WARN org.apache.hadoop.hdfs.server.datanode.VolumeScanner: Reporting bad BP-1800173197-10.204.68.5-1444425156296:blk_1170134484_96468685 on /dfs/dn\n2016-04-07 20:30:53,831 ERROR org.apache.hadoop.hdfs.server.datanode.VolumeScanner: VolumeScanner(/dfs/dn, DS-89b72832-2a8c-48f3-8235-48e6c5eb5ab3) exiting because of exception\njava.lang.NullPointerException\n at org.apache.hadoop.hdfs.server.datanode.DataNode.reportBadBlocks(DataNode.java:1018)\n at org.apache.hadoop.hdfs.server.datanode.VolumeScanner$ScanResultHandler.handle(VolumeScanner.java:287)\n at org.apache.hadoop.hdfs.server.datanode.VolumeScanner.scanBlock(VolumeScanner.java:443)\n at org.apache.hadoop.hdfs.server.datanode.VolumeScanner.runLoop(VolumeScanner.java:547)\n at org.apache.hadoop.hdfs.server.datanode.VolumeScanner.run(VolumeScanner.java:621)\n2016-04-07 20:30:53,832 INFO org.apache.hadoop.hdfs.server.datanode.VolumeScanner: VolumeScanner(/dfs/dn, DS-89b72832-2a8c-48f3-8235-48e6c5eb5ab3) exiting.\nI think the NPE comes from the volume variable in the following code snippet. Somehow the volume scanner know the volume, but the datanode can not lookup the volume using the block.\npublic void reportBadBlocks(ExtendedBlock block) throws IOException{\n BPOfferService bpos = getBPOSForBlock(block);\n FsVolumeSpi volume = getFSDataset().getVolume(block);\n bpos.reportBadBlocks(\n block, volume.getStorageID(), volume.getStorageType());\n }", "branch": "932aed64d77edcc8483a95c1ce31a4c9ae679446", "issue_url": "https://issues.apache.org/jira/browse/HDFS-10512", "fix_url": null, "issue_created": "2016-06-09", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": false, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "hdfs-10733", "system": "hdfs", "issue_number": "10733", "lite": false, "title": "NameNode terminated after full GC thinking QJM is unresponsive.", "description": "NameNode went into full GC while in AsyncLoggerSet.waitForWriteQuorum(). After completing GC it checks if the timeout for quorum is reached. If the GC was long enough the timeout can expire, and QuorumCall.waitFor() will throw TimeoutExcpetion. Finally FSEditLog.logSync() catches the exception and terminates NameNode.", "branch": "9130af3f74a7923fff3f80360ba043ab2c6558a9", "issue_url": "https://issues.apache.org/jira/browse/HDFS-10733", "fix_url": null, "issue_created": "2016-08-08", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hdfs-11583", "system": "hdfs", "issue_number": "11583", "lite": false, "title": "Parent spans are not initialized to NullScope for every DFSPacket", "description": "Each packet received by the run() method of DataStreamer class, uses the parents field of the DFSPacket to create a new dataStreamer span, which in turn creates a writeTo span as its child span. The parents field is initialized when the packet is added to the dataQueue and the value is initialized from the ThreadLocal. This is how HTrace handles spans.\nA TraceScope is created and initialized to NullScope before the loop which runs till the point when the stream is closed.\nConsider the following scenario, when the dataQueue contains multiple packets, only the first of which has a tracing enabled. The scope is initialized to the dataStreamer scope and a writeTo span is created as its child, which gets closed once the packet is sent out to a remote datanode. Before writeTo span is started, the dataStreamer scope is detached. So calling the close method on it doesn't do anything at the end of loop.\nThe second iteration will be using the stale value of the scope variable with a DFSPacket on which tracing is not enabled. This results in generation of an orphan writeTo spans which are being delivered to the SpanReceiver as registered in the TraceFramework. This may result in unlimited number of spans being generated and sent out to receiver.", "branch": "release-2.7.1", "issue_url": "https://issues.apache.org/jira/browse/HDFS-11583", "fix_url": null, "issue_created": "2017-03-27", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": false, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hdfs-11701", "system": "hdfs", "issue_number": "11701", "lite": false, "title": "NPE from Unresolved Host causes permanent DFSInputStream failures", "description": "We recently encountered the following NPE due to the DFSInputStream storing old cached block locations from hosts which could no longer resolve.\nCaused by: java.lang.NullPointerException\nat org.apache.hadoop.hdfs.DFSClient.isLocalAddress(DFSClient.java:1122)\nat org.apache.hadoop.hdfs.shortcircuit.DomainSocketFactory.getPathInfo(DomainSocketFactory.java:148)\nat org.apache.hadoop.hdfs.BlockReaderFactory.getBlockReaderLocal(BlockReaderFactory.java:474)\nat org.apache.hadoop.hdfs.BlockReaderFactory.build(BlockReaderFactory.java:354)\nat org.apache.hadoop.hdfs.DFSInputStream.blockSeekTo(DFSInputStream.java:662)\nat org.apache.hadoop.hdfs.DFSInputStream.seekToNewSource(DFSInputStream.java:1613)\nat org.apache.hadoop.fs.FSDataInputStream.seekToNewSource(FSDataInputStream.java:127)\nHBase related stack frames trimmed\nAfter investigating, the DFSInputStream appears to have been open for upwards of 3-4 weeks and had cached block locations from decommissioned nodes that no longer resolve in DNS and had been shutdown and removed from the cluster 2 weeks prior. If the DFSInputStream had refreshed its block locations from the name node, it would have received alternative block locations which would not contain the decommissioned data nodes. As the above NPE leaves the non-resolving data node in the list of block locations the DFSInputStream never refreshes the block locations and all attempts to open a BlockReader for the given blocks will fail.\nIn our case, we resolved the NPE by closing and re-opening every DFSInputStream in the cluster to force a purge of the block locations cache. Ideally, the DFSInputStream would re-fetch all block locations for a host which can't be resolved in DNS or at least the blocks requested.", "branch": "456705a07c8b80658950acc99f23086244c6b20f", "issue_url": "https://issues.apache.org/jira/browse/HDFS-11701", "fix_url": null, "issue_created": "2017-04-25", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "hdfs-13051", "system": "hdfs", "issue_number": "13051", "lite": true, "title": "Fix dead lock during async editlog rolling if edit queue is full", "description": "when doing rolleditlog it acquires fs write lock，then acquire FSEditLogAsync lock object，and write 3 EDIT(the second one override logEdit method and return true)\nin extremely case，when FSEditLogAsync's logSync is very slow，editPendingQ(default size 4096)is full，it case IPC thread can not offer edit object into editPendingQ when doing rolleditlog，it block on editPendingQ .put method，however it does't release FSEditLogAsync object lock, and edit.logEdit method in FSEditLogAsync.run thread can never acquire FSEditLogAsync object lock, it case dead lock\nstack trace like below\n\"Thread[Thread-44528,5,main]\" #130093 daemon prio=5 os_prio=0 tid=0x0000000002377000 nid=0x13fda waiting on condition [0x00007fb3297de000]\njava.lang.Thread.State: WAITING (parking)\nat sun.misc.Unsafe.park(Native Method)\nparking to wait for <0x00007fbd3cb96f58> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)\nat java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)\nat java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)\nat java.util.concurrent.ArrayBlockingQueue.put(ArrayBlockingQueue.java:353)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLogAsync.enqueueEdit(FSEditLogAsync.java:156)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLogAsync.logEdit(FSEditLogAsync.java:118)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLog.logCancelDelegationToken(FSEditLog.java:1008)\nat org.apache.hadoop.hdfs.server.namenode.FSNamesystem.logExpireDelegationToken(FSNamesystem.java:7635)\nat org.apache.hadoop.hdfs.security.token.delegation.DelegationTokenSecretManager.logExpireToken(DelegationTokenSecretManager.java:395)\nlocked <0x00007fbd3cbae500> (a java.lang.Object)\nat org.apache.hadoop.hdfs.security.token.delegation.DelegationTokenSecretManager.logExpireToken(DelegationTokenSecretManager.java:62)\nat org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager.removeExpiredToken(AbstractDelegationTokenSecretManager.java:604)\nat org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager.access$400(AbstractDelegationTokenSecretManager.java:54)\nat org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager$ExpiredTokenRemover.run(AbstractDelegationTokenSecretManager.java:656)\nat java.lang.Thread.run(Thread.java:745)\n\"FSEditLogAsync\" #130072 daemon prio=5 os_prio=0 tid=0x000000000715b800 nid=0x13fbf waiting for monitor entry [0x00007fb32c51a000]\njava.lang.Thread.State: BLOCKED (on object monitor)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLog.doEditTransaction(FSEditLog.java:443)\nwaiting to lock <0x00007fbcbc131000> (a org.apache.hadoop.hdfs.server.namenode.FSEditLogAsync)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLogAsync$Edit.logEdit(FSEditLogAsync.java:233)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLogAsync.run(FSEditLogAsync.java:177)\nat java.lang.Thread.run(Thread.java:745)\n\"IPC Server handler 47 on 53310\" #337 daemon prio=5 os_prio=0 tid=0x00007fe659d46000 nid=0x4c62 waiting on condition [0x00007fb32fe52000]\njava.lang.Thread.State: WAITING (parking)\nat sun.misc.Unsafe.park(Native Method)\nparking to wait for <0x00007fbd3cb96f58> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)\nat java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)\nat java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)\nat java.util.concurrent.ArrayBlockingQueue.put(ArrayBlockingQueue.java:353)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLogAsync.enqueueEdit(FSEditLogAsync.java:156)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLogAsync.logEdit(FSEditLogAsync.java:118)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLog.endCurrentLogSegment(FSEditLog.java:1251)\nlocked <0x00007fbcbc131000> (a org.apache.hadoop.hdfs.server.namenode.FSEditLogAsync)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLog.rollEditLog(FSEditLog.java:1190)\nlocked <0x00007fbcbc131000> (a org.apache.hadoop.hdfs.server.namenode.FSEditLogAsync)\nat org.apache.hadoop.hdfs.server.namenode.FSImage.rollEditLog(FSImage.java:1235)\nat org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:6463)\nat org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:1062)\nat org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:142)\nat org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:12025)\nat org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:617)\nat org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1073)\nat org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2141)\nat org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2137)\nat java.security.AccessController.doPrivileged(Native Method)\nat javax.security.auth.Subject.doAs(Subject.java:422)\nat org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1743)\nat org.apache.hadoop.ipc.Server$Handler.run(Server.java:2135)", "branch": "96892c469b16c5aaff1b7c42f66f820344256bc2", "issue_url": "https://issues.apache.org/jira/browse/HDFS-13051", "fix_url": "https://issues.apache.org/jira/secure/attachment/12909545/deadlock.patch", "issue_created": "2018-01-23", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "hdfs-13101", "system": "hdfs", "issue_number": "13101", "lite": false, "title": "Yet another fsimage corruption related to snapshot", "description": "FSImage corruption happened after HDFS snapshots were taken. Cluster was not used\nat that time.\nWhen namenode restarts it reported NULL pointer exception:\n15/11/07 10:01:15 INFO namenode.FileJournalManager: Recovering unfinalized segments in /tmp/fsimage_checker_5857/fsimage/current\n15/11/07 10:01:15 INFO namenode.FSImage: No edit log streams selected.\n15/11/07 10:01:18 INFO namenode.FSImageFormatPBINode: Loading 1370277 INodes.\n15/11/07 10:01:27 ERROR namenode.NameNode: Failed to start namenode.\njava.lang.NullPointerException\n at org.apache.hadoop.hdfs.server.namenode.INodeDirectory.addChild(INodeDirectory.java:531)\n at org.apache.hadoop.hdfs.server.namenode.FSImageFormatPBINode$Loader.addToParent(FSImageFormatPBINode.java:252)\n at org.apache.hadoop.hdfs.server.namenode.FSImageFormatPBINode$Loader.loadINodeDirectorySection(FSImageFormatPBINode.java:202)\n at org.apache.hadoop.hdfs.server.namenode.FSImageFormatProtobuf$Loader.loadInternal(FSImageFormatProtobuf.java:261)\n at org.apache.hadoop.hdfs.server.namenode.FSImageFormatProtobuf$Loader.load(FSImageFormatProtobuf.java:180)\n at org.apache.hadoop.hdfs.server.namenode.FSImageFormat$LoaderDelegator.load(FSImageFormat.java:226)\n at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:929)\n at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:913)\n at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImageFile(FSImage.java:732)\n at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:668)\n at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:281)\n at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:1061)\n at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:765)\n at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:584)\n at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:643)\n at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:810)\n at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:794)\n at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1487)\n at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1553)\n15/11/07 10:01:27 INFO util.ExitUtil: Exiting with status 1\nCorruption happened after \"07.11.2015 00:15\", and after that time blocks ~9300 blocks were invalidated that shouldn't be.\nAfter recovering FSimage I discovered that around ~9300 blocks were missing.", "branch": "167acd87daf61be9a27dfb5af6e7cbacb96e44de", "issue_url": "https://issues.apache.org/jira/browse/HDFS-13101", "fix_url": "https://issues.apache.org/jira/secure/attachment/12977155/HDFS-13101.004.patch", "issue_created": "2018-02-01", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hdfs-13179", "system": "hdfs", "issue_number": "13179", "lite": false, "title": "TestLazyPersistReplicaRecovery#testDnRestartWithSavedReplicas fails intermittently", "description": "The error caused by TimeoutException because the test is waiting to ensure that the file is replicated to DISK storage but the replication can't be finished to DISK during the 30s timeout in ensureFileReplicasOnStorageType(), but the file is still on RAM_DISK - so there is no data loss.\nAdding the following to TestLazyPersistReplicaRecovery.java:56 essentially fixes the flakiness.\n try {\n ensureFileReplicasOnStorageType(path1, DEFAULT);\n }catch (TimeoutException t){\n LOG.warn(\"We got \\\"\" + t.getMessage() + \"\\\" so trying to find data on RAM_DISK\");\n ensureFileReplicasOnStorageType(path1, RAM_DISK);\n }\n }\nSome thoughts:\nSuccessful and failed tests run similar to the point when datanode restarts. Restart line is the following in the log: LazyPersistTestCase - Restarting the DataNode\nThere is a line which only occurs in the failed test: addStoredBlock: Redundant addStoredBlock request received for blk_1073741825_1001 on node 127.0.0.1:49455 size 5242880\nThis redundant request at BlockManager#addStoredBlock could be the main reason for the test fail. Something wrong with the gen stamp? Corrupt replicas?\n=============================\nCurrent fail ratio based on my test of TestLazyPersistReplicaRecovery:\n1000 runs, 34 failures (3.4% fail)\nFailure rate analysis:\nTestLazyPersistReplicaRecovery.testDnRestartWithSavedReplicas: 3.4%\n33 failures caused by:\njava.util.concurrent.TimeoutException: Timed out waiting for condition. Thread diagnostics: Timestamp: 2018-01-05 11:50:34,964 \"IPC Server handler 6 on 39589\" \n1 failure caused by:\njava.net.BindException: Problem binding to [localhost:56729] java.net.BindException: Address already in use; For more details see: http://wiki.apache.org/hadoop/BindException at org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery.testDnRestartWithSavedReplicas(TestLazyPersistReplicaRecovery.java:49) Caused by: java.net.BindException: Address already in use at org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery.testDnRestartWithSavedReplicas(TestLazyPersistReplicaRecovery.java:49)\n=============================\nExample stacktrace:\nTimed out waiting for condition. Thread diagnostics:\nTimestamp: 2017-11-01 10:36:49,499\n\"Thread-1\" prio=5 tid=13 runnable\njava.lang.Thread.State: RUNNABLE\nat java.lang.Thread.dumpThreads(Native Method)\nat java.lang.Thread.getAllStackTraces(Thread.java:1610)\nat org.apache.hadoop.test.TimedOutTestsListener.buildThreadDump(TimedOutTestsListener.java:87)\nat org.apache.hadoop.test.TimedOutTestsListener.buildThreadDiagnosticString(TimedOutTestsListener.java:73)\nat org.apache.hadoop.test.GenericTestUtils.waitFor(GenericTestUtils.java:369)\nat org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.LazyPersistTestCase.ensureFileReplicasOnStorageType(LazyPersistTestCase.java:140)\nat org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery.testDnRestartWithSavedReplicas(TestLazyPersistReplicaRecovery.java:54)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\nat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\nat java.lang.reflect.Method.invoke(Method.java:498)", "branch": "5abd0148eb9484381c7ff92b4bfab9ac8a81c681", "issue_url": "https://issues.apache.org/jira/browse/HDFS-13179", "fix_url": "https://issues.apache.org/jira/secure/attachment/12991953/HDFS-13179.003.patch", "issue_created": "2018-02-22", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "hdfs-13292", "system": "hdfs", "issue_number": "13292", "lite": false, "title": "Crypto command should give proper exception when trying to set key on existing EZ directory", "description": "Scenario:\nCreate a Dir\nCreate EZ for the above dir with Key1\nAgain you can try to create ZONE for same directory with Diff Key i.e Key2\nhadoopclient> hadoop key list\nListing keys for KeyProvider: org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider@152aa092\nkey2\nkey1\nhadoopclient> hdfs dfs -mkdir /kms\nhadoopclient> hdfs dfs -put bigdata_env /kms/file1\nhadoopclient> hdfs crypto -createZone -keyName key1 -path /kms\nRemoteException: Attempt to create an encryption zone for a non-empty directory.\nhadoopclient> hdfs dfs -rmr /kms/file1\nrmr: DEPRECATED: Please use '-rm -r' instead.\nDeleted /kms/file1\nhadoopclient> hdfs crypto -createZone -keyName key1 -path /kms\nAdded encryption zone /kms\nhadoopclient> hdfs crypto -createZone -keyName key2 -path /kms\nRemoteException: Attempt to create an encryption zone for a non-empty directory.\nhadoopclient>\n \nActual Output:\n===========\nException should be Like Dir already having the ZONE will not allow to create new ZONE on this Dir\nExpected Output:\n=============\nRemoteException:Attempt to create an encryption zone for non-empty directory", "branch": "00ebec89f101347a5da44657e388b30c57ed9deb", "issue_url": "https://issues.apache.org/jira/browse/HDFS-13292", "fix_url": null, "issue_created": "2018-03-15", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hdfs-13893", "system": "hdfs", "issue_number": "13893", "lite": false, "title": "DiskBalancer: no validations for Disk balancer commands", "description": "1 Run the Disk Balancer commands with extra arguments passing \n \nhadoopclient> hdfs diskbalancer -plan hostname --thresholdPercentage 2 *sgfsdgfs*\n2018-08-31 14:57:35,454 INFO planner.GreedyPlanner: Starting plan for Node : hostname:50077\n2018-08-31 14:57:35,457 INFO planner.GreedyPlanner: Disk Volume set fb67f00c-e333-4f38-a3a6-846a30d4205a Type : DISK plan completed.\n2018-08-31 14:57:35,457 INFO planner.GreedyPlanner: Compute Plan for Node : hostname:50077 took 23 ms\n2018-08-31 14:57:35,457 INFO command.Command: Writing plan to:\n2018-08-31 14:57:35,457 INFO command.Command: /system/diskbalancer/2018-Aug-31-14-57-35/hostname.plan.json\nWriting plan to:\n/system/diskbalancer/2018-Aug-31-14-57-35/hostname.plan.json\nExpected Output:-\n=============\nDisk balancer commands should be fail if we pass any invalid arguments or extra arguments", "branch": "98d20656433cdec76c2108d24ff3b935657c1e80", "issue_url": "https://issues.apache.org/jira/browse/HDFS-13893", "fix_url": "https://issues.apache.org/jira/secure/attachment/12949642/HDFS-13893.003.patch", "issue_created": "2018-09-04", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "hdfs-15175", "system": "hdfs", "issue_number": "15175", "lite": true, "title": "Multiple CloseOp shared block instance causes the standby namenode to crash when rolling editlog", "description": "Crash exception\n2020-02-16 09:24:46,426 [507844305] - ERROR [Edit log tailer:FSEditLogLoader@245] - Encountered exception on operation CloseOp [length=0, inodeId=0, path=..., replication=3, mtime=1581816138774, atime=1581814760398, blockSize=536870912, blocks=[blk_5568434562_4495417845], permissions=da_music:hdfs:rw-r-----, aclEntries=null, clientName=, clientMachine=, overwrite=false, storagePolicyId=0, opCode=OP_CLOSE, txid=32625024993]\njava.io.IOException: File is not under construction: ......\nat org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.applyEditLogOp(FSEditLogLoader.java:442)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadEditRecords(FSEditLogLoader.java:237)\nat org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadFSEdits(FSEditLogLoader.java:146)\nat org.apache.hadoop.hdfs.server.namenode.FSImage.loadEdits(FSImage.java:891)\nat org.apache.hadoop.hdfs.server.namenode.FSImage.loadEdits(FSImage.java:872)\nat org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer.doTailEdits(EditLogTailer.java:262)\nat org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.doWork(EditLogTailer.java:395)\nat org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.access$300(EditLogTailer.java:348)\nat org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread$1.run(EditLogTailer.java:365)\nat java.security.AccessController.doPrivileged(Native Method)\nat javax.security.auth.Subject.doAs(Subject.java:360)\nat org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1873)\nat org.apache.hadoop.security.SecurityUtil.doAsLoginUserOrFatal(SecurityUtil.java:479)\nat org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.run(EditLogTailer.java:361)\n \nEditlog\n\nOP_REASSIGN_LEASE\n\n32625021150\nDFSClient_NONMAPREDUCE_-969060727_197760\n......\nDFSClient_NONMAPREDUCE_1000868229_201260\n\n\n......\n\nOP_CLOSE\n\n32625023743\n0\n0\n......\n3\n1581816135883\n1581814760398\n536870912\n\n\nfalse\n\n5568434562\n185818644\n4495417845\n\n\nda_music\nhdfs\n416\n\n\n\n......\n\nOP_TRUNCATE\n\n32625024049\n......\nDFSClient_NONMAPREDUCE_1000868229_201260\n......\n185818644\n1581816136336\n\n5568434562\n185818648\n4495417845\n\n\n\n......\n\nOP_CLOSE\n\n32625024993\n0\n0\n......\n3\n1581816138774\n1581814760398\n536870912\n\n\nfalse\n\n5568434562\n185818644\n4495417845\n\n\nda_music\nhdfs\n416\n\n\n\n \n \nThe block size should be 185818648 in the first CloseOp. When truncate is used, the block size becomes 185818644. The CloseOp/TruncateOp/CloseOp is synchronized to the JournalNode in the same batch. The block used by CloseOp twice is the same instance, which causes the first CloseOp has wrong block size. When SNN rolling Editlog, TruncateOp does not make the file to the UnderConstruction state. Then, when the second CloseOp is executed, the file is not in the UnderConstruction state, and SNN crashes.", "branch": "3c8a48e681babe4038e49205624e7be183b3466e", "issue_url": "https://issues.apache.org/jira/browse/HDFS-15175", "fix_url": "https://issues.apache.org/jira/secure/attachment/13005703/HDFS-15175-trunk.1.patch", "issue_created": "2018-02-22", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ignite-4205", "system": "ignite", "issue_number": "4205", "lite": false, "title": "", "description": "CassandraCacheStore.loadCache() method starts a generic thread pool for parallel data load. Threads in this thread pool can't deserialize Ignite internal objects (e.g. IgniteKernal) which can cause unexpected behavior. Here is one of the scenarios:\n\n There is column in Cassandra which stores an object as BLOB using JavaSerializer.\n CacheConfiguration.storeKeepBinary is true.\n When an object is saved, it's passed to the store as an instance of BinaryObject which is converted to a byte array and saved in Cassandra.\n When the same object is loaded in loadCache, the store takes the byte array and tries to convert it to BinaryObject. But it can't because this implies calling IgnitionEx.localIgnite() from non-Ignite thread.\n\nTo fix this we need to provide a thread factory that will create instances of IgniteThread and use it in the pool that loads the data.\n\nMost likely the same issue exists in CacheAbstractJdbcStore.\n\nAnd in general, any threads created by Ignite internals should be IgniteThread-s. This should be revisited.", "branch": "90717b4b7230ca5f5e0fd9318d0aa0a6f5e48064", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-4205", "fix_url": null, "issue_created": "2016-11-10", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ignite-6860", "system": "ignite", "issue_number": "6860", "lite": true, "title": "", "description": "Having the stack trace\n\nCaused by: org.apache.ignite.binary.BinaryObjectException: Failed to marshal object with optimized marshaller: [org.apache.logging.log4j.core.config.AppenderControl@302e61a8]\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:186)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteCollection(BinaryWriterExImpl.java:764)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeCollectionField(BinaryWriterExImpl.java:1274)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:631)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteMap(BinaryWriterExImpl.java:786)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:699)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObjectArray(BinaryWriterExImpl.java:743)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectArrayField(BinaryWriterExImpl.java:1266)\n at org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:626)\n at org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)\n at org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:248)\n at org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)\n at org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)\n at org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9845)\n at org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1373)\n at org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:660)\n at org.apache.ignite.internal.processors.task.GridTaskWorker.access$000(GridTaskWorker.java:112)\n at org.apache.ignite.internal.processors.task.GridTaskWorker$1.send(GridTaskWorker.java:223)\n at com.sbt.dpl.gridgain.DistributedCollectTask.sendCollectJobs(DistributedCollectTask.java:167)\n at com.sbt.dpl.gridgain.DistributedCollectTask.result(DistributedCollectTask.java:137)\n ... 14 common frames omitted\nCaused by: org.apache.ignite.IgniteCheckedException: Failed to serialize object: [org.apache.logging.log4j.core.config.AppenderControl@302e61a8]\n at org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:206)\n at org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)\n at org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9845)\n at org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:179)\n ... 160 common frames omitted\nCaused by: java.io.IOException: java.io.IOException: java.io.IOException: java.lang.NoClassDefFoundError: org/apache/commons/csv/CSVFormat\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:339)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:159)\n at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:201)\n ... 163 common frames omitted\nCaused by: java.io.IOException: java.io.IOException: java.lang.NoClassDefFoundError: org/apache/commons/csv/CSVFormat\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:339)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:159)\n at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)\n at java.util.concurrent.CopyOnWriteArrayList.writeObject(CopyOnWriteArrayList.java:973)\n at sun.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)\n at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n at java.lang.reflect.Method.invoke(Method.java:498)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:333)\n ... 172 common frames omitted\nCaused by: java.io.IOException: java.lang.NoClassDefFoundError: org/apache/commons/csv/CSVFormat\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:339)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:159)\n at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)\n at java.util.concurrent.CopyOnWriteArrayList.writeObject(CopyOnWriteArrayList.java:973)\n at sun.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)\n at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n at java.lang.reflect.Method.invoke(Method.java:498)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:333)\n ... 197 common frames omitted\nCaused by: java.lang.NoClassDefFoundError: org/apache/commons/csv/CSVFormat\n at java.lang.Class.getDeclaredMethods0(Native Method)\n at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)\n at java.lang.Class.getDeclaredMethod(Class.java:2128)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.(OptimizedClassDescriptor.java:355)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:214)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:780)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeLinkedHashMap(OptimizedObjectOutputStream.java:440)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:765)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeFields(OptimizedObjectOutputStream.java:531)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:343)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:827)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:239)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:159)\n at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)\n at java.util.concurrent.CopyOnWriteArrayList.writeObject(CopyOnWriteArrayList.java:973)\n at sun.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)\n at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n at java.lang.reflect.Method.invoke(Method.java:498)\n at org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeSerializable(OptimizedObjectOutputStream.java:333)\n ... 218 common frames omitted\nCaused by: java.lang.ClassNotFoundException: org.apache.commons.csv.CSVFormat\n at java.net.URLClassLoader.findClass(URLClassLoader.java:381)\n at java.lang.ClassLoader.loadClass(ClassLoader.java:424)\n at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)\n at java.lang.ClassLoader.loadClass(ClassLoader.java:357)\n ... 263 common frames omitted\n\nWe really coudn't event guess which field of which object (type) cause the ClassNotFoundException.\n\nThe context information about what field and what object type cause the problem should be logged on each level of call stack.\n", "branch": "7366809ed0ea7a943e1c80079fdbeb556ee86245", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-6860", "fix_url": null, "issue_created": "2017-11-10", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Hard", "distributed": false, "contains_analysis": false, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ignite-9133", "system": "ignite", "issue_number": "9133", "lite": true, "title": "", "description": "In the cases when DHT transaction is empty (i.e. no keys were enlisted) after the enlist step, we need to rollback local DHT transaction to exclude it from the further transaction flow in order to performance increasing.\n\nAn ordinary Dht tx rollback GridDhtTxLocal#rollbackDhtLocalAsync is not suitable in this situation because it adds tx to IgniteTxManager#completedVersHashMap which is unacceptable because this action prevents possible Dht transaction creation if the next tx statements enlist some keys at this node in the future. As well as direct tx map cleaning by means of IgniteTxManager#rollbackTx(tx, true, true) is not an aid because leads to grid hanging due to undiscovered reasons. In order to reproduce hanging you need to reapply commit d231a81 and run CacheMvccPartitionedSqlCoordinatorFailoverTest. Example of hanged thread stack is listed below.\n\nOur goal is the proper Dht transaction rollback without adding it to IgniteTxManager#completedVersHashMap.\n\nThread [name=\"writer-2\", id=2281, state=WAITING, blockCnt=40, waitCnt=10260]\n at sun.misc.Unsafe.park(Native Method)\n at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)\n at o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)\n at o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)\n at o.a.i.i.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:560)\n at o.a.i.i.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:185)\n at o.a.i.i.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:358)\n at o.a.i.i.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:2132)\n at o.a.i.i.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2083)\n at o.a.i.i.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)\n at o.a.i.i.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)\n at o.a.i.i.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)\n at o.a.i.i.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2682)\n at o.a.i.i.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)\n at o.a.i.i.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:668)\n at o.a.i.i.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:619)\n at o.a.i.i.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)\n at o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest.removeSql(CacheMvccAbstractTest.java:832)\n at o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest.access$400(CacheMvccAbstractTest.java:104)\n at o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest$2.apply(CacheMvccAbstractTest.java:494)\n at o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest$2.apply(CacheMvccAbstractTest.java:401)\n at o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1294)\n at o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1289)\n at o.a.i.testframework.GridTestThread.run(GridTestThread.java:86)\n", "branch": "824939ba1f238621bd89a5ff445c6932c79e5db9", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-9133", "fix_url": null, "issue_created": "2018-07-30", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": null, "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ignite3-15596", "system": "ignite3", "issue_number": "15596", "lite": false, "title": "", "description": "Calcite. java.lang.Integer cannot be cast to java.lang.Long with JOIN and EXISTS.\nExport \n\nstatement ok\nCREATE TABLE tbl(a TINYINT, b SMALLINT, c INTEGER, d BIGINT, e VARCHAR, f DATE, g TIMESTAMP)\n\nstatement ok\nINSERT INTO tbl VALUES (1, 2, 3, 4, '5', DATE '1992-01-01', TIMESTAMP '1992-01-01 00:00:00')\n\nquery I\nSELECT 1 FROM tbl t1 JOIN tbl t2 ON (t1.d=t2.d) WHERE EXISTS(SELECT t1.c FROM tbl t3 WHERE t1.d+t3.c<100 AND EXISTS(SELECT t2.f < DATE '2000-01-01'))\n----\n1\n\n../exists/test_complex_nested_correlated_subquery.test[_ignore]\n\nCaused by: java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long\n at SC.execute(Unknown Source)\n at org.apache.ignite.internal.processors.query.calcite.exec.exp.ExpressionFactoryImpl$BiPredicateImpl.test(ExpressionFactoryImpl.java:448)\n at org.apache.ignite.internal.processors.query.calcite.exec.rel.NestedLoopJoinNode$InnerJoin.join(NestedLoopJoinNode.java:283)\n at org.apache.ignite.internal.processors.query.calcite.exec.rel.NestedLoopJoinNode.endRight(NestedLoopJoinNode.java:194)\n\n", "branch": "ed519fb2fa2a89e11a8ab7fad3069f7e1f7d74b3", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-15596", "fix_url": null, "issue_created": "2021-09-24", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ignite3-15724", "system": "ignite3", "issue_number": "15724", "lite": false, "title": "", "description": "MetastorageManager uses incorrect predicate in order to create corresponding raft group service Currently, when the MetaStorageManager is started, the metastorage raft group is reduced to online nodes that satisfies to the metaStorageNodesContainsLocPred.\n\nString[] metastorageNodes = this.locCfgMgr.configurationRegistry().getConfiguration(NodeConfiguration.KEY).metastorageNodes().value();\n\nPredicate metaStorageNodesContainsLocPred =\n clusterNode -> Arrays.asList(metastorageNodes).contains(clusterNode.name());\n\n...\n \nList metaStorageMembers = clusterNetSvc.topologyService().allMembers().stream()\n .filter(metaStorageNodesContainsLocPred)\n .collect(Collectors.toList());\n\nThat is actually a subset of required nodes. In that case, only the first node creates the metastorage raft group, and the second one will be rejected with the following messages:\n\n[WARNING][%ITIgnitionTest_testNodesStartWithBootstrapConfiguration_3344%JRaft-Request-Processor-27][NodeImpl] Node ignore PreVoteRequest from 172.24.144.1:3345 as it is not in conf .\n[WARNING][%ITIgnitionTest_testNodesStartWithBootstrapConfiguration_3345%JRaft-Response-Processor-1][NodeImpl] Node received invalid PreVoteResponse from 172.24.144.1:3344, term 1, expect=0.\n\nIt seems that this issue cannot be properly fixed until is IGNITE-14414 is implemented. For now, we can just prohibit creating a metastorage group greater than one node.\n", "branch": "2abd5b9f5525ac2ea9314e45cea9deb6be871418", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-15724", "fix_url": null, "issue_created": "2021-10-11", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ignite3-17428", "system": "ignite3", "issue_number": "17428", "lite": false, "title": "", "description": "Current version of TableManager#tableAsyncInternal can possibly not detect table that is being created while tableAsyncInternal is called. Scenario:\n\n tableAsyncInternal checks tablesByIdVv.latest() and there is no table\n the table creation started, table metadata appears in meta storage\n TableEvent.CREATE is fired\n tableAsyncInternal registers a listener for TableEvent.CREATE (after it is fired for corresponding table)\n tableAsyncInternal checks tablesByIdVv.latest() once again and there still is no table, because the table creation is not completed\n !isTableConfigured(id) condition returns false as the table is present in meta storage\n if (tbl != null && getTblFut.complete(tbl) || !isTableConfigured(id) && getTblFut.complete(null)) evaluates false and the future created fot getTable never completes.\n\nPossibly we should use VersionedValue#whenComplete instead of creating listener for event. The table is present in map wrapped in versioned value only when the table creation is completed, and whenComplete allows to create a callback to check the table presence.\n\nThe same problem is presented for SchemaManager when we get schema in SchemaManager#tableSchema\n\nPossible fix for SchemaManager is to use this pattern\n\n registriesVv.whenComplete((token, val, e) -> {\n if (schemaVer <= val.get(tblId).lastSchemaVersion()) {\n fut.complete(getSchemaDescriptorLocally(schemaVer, tblCfg));\n }\n });\n\ninstead of creating listener for CREATE event. The same approach can be used for TableManager\n", "branch": "2c4d07597235ef54b23c9726a755e5876b98e1a1", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-17428", "fix_url": null, "issue_created": "2022-07-27", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ignite3-20498", "system": "ignite3", "issue_number": "20498", "lite": false, "title": "", "description": "\nPrevent potential catalog version order violations.\nCurrently, catalog versions are stored in an ordered structure. The activation timestamp is used as a key, which depends on the configuration property \"schemaSync.delayDuration\".\n\nChanges to \"delayDuration\" parameter in runtime may lead to a violation of the order in which catalog versions are stored. That is, the old version may be saved with a bigger timestamp than the newer one.\n\nAs a result, the manager can return incorrect (older) version of the catalog using a timestamp.\n\nreproducer:\n\npublic class CatalogDelayDurationChangeTest extends BaseIgniteAbstractTest {\n private static final String NODE_NAME = \"node1\";\n private static final String TABLE_NAME = \"test1\";\n private final HybridClock clock = new HybridClockImpl();\n private final AtomicLong delayFromConfig = new AtomicLong();\n\n @Test\n public void testChangeDelayDuration() {\n CatalogManager catalogMgr = createManager();\n\n // Prepare schema changes.\n ColumnParams column = ColumnParams.builder().name(\"ID\").type(ColumnType.INT32).build();\n CatalogCommand cmd1 = BaseCatalogManagerTest.createTableCommand(TABLE_NAME, List.of(column), List.of(\"ID\"), null);\n CatalogCommand cmd2 = BaseCatalogManagerTest.createTableCommand(\"test2\", List.of(column), List.of(\"ID\"), null);\n\n // Make first schema change with delay = 1000.\n delayFromConfig.set(1_000);\n CompletableFuture schemaChangeFuture0 = catalogMgr.execute(cmd1);\n\n // Make second schema change with delay = 1.\n delayFromConfig.set(1);\n CompletableFuture schemaChangeFuture1 = catalogMgr.execute(cmd2);\n\n assertThat(schemaChangeFuture0, willCompleteSuccessfully());\n assertThat(schemaChangeFuture1, willCompleteSuccessfully());\n\n // Make sure that we are getting the latest version of the schema using current timestamp.\n int latestVer = catalogMgr.latestCatalogVersion();\n int currentTsVer = catalogMgr.activeCatalogVersion(clock.now().longValue());\n assertThat(currentTsVer, equalTo(latestVer));\n }\n\n private CatalogManager createManager() {\n VaultManager vault = new VaultManager(new InMemoryVaultService());\n MetaStorageManager metastore = StandaloneMetaStorageManager.create(vault, new SimpleInMemoryKeyValueStorage(NODE_NAME));\n UpdateLog updateLog = spy(new UpdateLogImpl(metastore));\n ClockWaiter clockWaiter = spy(new ClockWaiter(NODE_NAME, clock));\n CatalogManager manager = new CatalogManagerImpl(updateLog, clockWaiter, delayFromConfig::get, () -> 10L);\n\n vault.start();\n metastore.start();\n clockWaiter.start();\n manager.start();\n\n metastore.deployWatches().join();\n\n return manager;\n }\n}\n\n", "branch": "7a1540365d89d188da1f0d22c27c96ddc21485ac", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-20498", "fix_url": null, "issue_created": "2023-09-26", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ignite3-21776", "system": "ignite3", "issue_number": "21776", "lite": false, "title": "", "description": "\"Create table if not exists\" not a thread safe : In two parallel clients:\n\n1) Run DDL (using two clients):\n\n```\n\ncreate table if not exists parallelCreateTable0\n\n(id INTEGER not null,\n\nval VARCHAR not null,\n\nprimary key (id))\n\n```\n\n2) Get parallelCreateTable0 using ignite.tables() API or select from jdbc\n\nExpected result:\n\n One client creates the table, second one - wait table created\n Both client can use the table\n\nActual result:\n\n One client creates the table, second one return control immediatly\n Second client fails to use the table, the first one works as expected after the table creating finished.\n\n", "branch": "b08fbb60872f5c88209152992bce392f92109f87", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-21776", "fix_url": null, "issue_created": "2024-03-18", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ignite3-21827", "system": "ignite3", "issue_number": "21827", "lite": true, "title": "", "description": "Union returns incorrect result for NUMERIC/DECIMAL and INT columns\n\nSimple reproducer:\n\n sql(\"CREATE TABLE t0(id INT PRIMARY KEY, val INT)\");\n sql(\"CREATE TABLE t1(id INT PRIMARY KEY, val DECIMAL)\");\n sql(\"INSERT INTO t0 VALUES (1, 10)\");\n sql(\"INSERT INTO t1 VALUES (1, 10)\");\n\n assertQuery(\"SELECT id, val from t0 UNION select id, val from t1\")\n .returns(1, new BigDecimal(10))\n .ordered()\n .check();\n\nCheck fails:\n\njava.lang.AssertionError: Collections sizes are not equal:\n Expected: 1\n Actual: 2\n\n \n\nThe actual result for such a query contains duplicate values.\n\n 1 10\n 1 10\n\n", "branch": "166ade294eb8311cb0dc46bcdcedb3620bea7eb9", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-21827", "fix_url": null, "issue_created": "2024-03-22", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ignite3-22597", "system": "ignite3", "issue_number": "22597", "lite": true, "title": "", "description": "Motivation\n\nThe trace id is generated at the place where the original exception was created and should be propogated to other derevatives. Right now, we send only an exception message and class name to the RAFT listener response.\n\nprivate void sendSMError(RpcContext ctx, Throwable th, boolean compacted) {\n RpcRequests.SMErrorResponse resp = factory.sMErrorResponse()\n .error(compacted ? new SMCompactedThrowable(th) : new SMFullThrowable(th))\n .build();\n\n ctx.sendResponse(resp);\n\n LOG.info(\"Error occurred on a user's state machine\", th);\n}\n\nHence, we cannot restore the trace id and create an exception with a new trace id:\n\nThrowable restoredTh = (Throwable) Class.forName(compactedThrowable.throwableClassName())\n .getConstructor(String.class)\n .newInstance(compactedThrowable.throwableMessage());\n\nfut.completeExceptionally(restoredTh);\n\nDefinition of done\n\n Both attached logs should be logged with the same trace id.\n Massage in the RAFT listener should be logged in error (or warning) level.\n", "branch": "787e868ede5a489b49c4cd9d58d3c467b10e46ed", "issue_url": "https://issues.apache.org/jira/browse/IGNITE-22597", "fix_url": null, "issue_created": "2024-06-27", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": null, "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kafka-6446", "system": "kafka", "issue_number": "6446", "lite": true, "title": "KafkaProducer with transactionId endless waits when bootstrap server is down", "description": "When bootstrap server is down, a KafkaProducer with transactionId endless waits on initTransactions. \n\nThe timeouts don't apply to that operation: don't honor the TRANSACTION_TIMEOUT_CONFIG.\n\nAttached an example of my code to reproduce the scenario.\n\nimport java.util.HashMap;\nimport java.util.Map;\n\nimport org.apache.kafka.clients.producer.KafkaProducer;\nimport org.apache.kafka.clients.producer.ProducerConfig;\n\npublic class Test {\n \n public static void main(String[] args) {\n \n final KafkaProducer producer = new KafkaProducer(producerConfigs());\n \n producer.initTransactions();\n } \n \n private static Map producerConfigs() {\n \n final Map props = new HashMap<>();\n \n props.put(ProducerConfig.BOOTSTRAP_SERVERS_CONFIG, \"192.168.56.1:9092\");\n props.put(ProducerConfig.KEY_SERIALIZER_CLASS_CONFIG, \"org.apache.kafka.common.serialization.StringSerializer\");\n props.put(ProducerConfig.VALUE_SERIALIZER_CLASS_CONFIG, \"org.apache.kafka.common.serialization.StringSerializer\");\n \n props.put(ProducerConfig.RETRIES_CONFIG, 1);\n props.put(ProducerConfig.MAX_IN_FLIGHT_REQUESTS_PER_CONNECTION, 1);\n \n props.put(ProducerConfig.TRANSACTION_TIMEOUT_CONFIG, 1000);\n props.put(ProducerConfig.TRANSACTIONAL_ID_CONFIG, \"transactionId\");\n \n props.put(ProducerConfig.REQUEST_TIMEOUT_MS_CONFIG, 1000);\n props.put(ProducerConfig.MAX_BLOCK_MS_CONFIG, 1000);\n \n return props;\n }\n \n}", "branch": "1.0.0", "issue_url": "https://issues.apache.org/jira/browse/KAFKA-6446", "fix_url": "https://github.com/apache/kafka/pull/4563", "issue_created": "2018-01-15", "severity": "Critical", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kafka-7044", "system": "kafka", "issue_number": "7044", "lite": true, "title": "kafka-consumer-groups.sh NullPointerException describing round robin or sticky assignors", "description": "We've recently moved to using the round robin assignor for one of our consumer groups, and started testing the sticky assignor. In both cases, using Kafka 1.1.0 we get a null pointer exception unless the group being described is rebalancing:\n\nkafka-consumer-groups --bootstrap-server fqdn:9092 --describe --group groupname-for-consumer\n\nError: Executing consumer group command failed due to null\n[2018-06-12 01:32:34,179] DEBUG Exception in consumer group command (kafka.admin.ConsumerGroupCommand$)\njava.lang.NullPointerException\nat scala.Predef$.Long2long(Predef.scala:363)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService$$anonfun$getLogEndOffsets$2.apply(ConsumerGroupCommand.scala:612)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService$$anonfun$getLogEndOffsets$2.apply(ConsumerGroupCommand.scala:610)\nat scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)\nat scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)\nat scala.collection.immutable.List.foreach(List.scala:392)\nat scala.collection.TraversableLike$class.map(TraversableLike.scala:234)\nat scala.collection.immutable.List.map(List.scala:296)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService.getLogEndOffsets(ConsumerGroupCommand.scala:610)\nat kafka.admin.ConsumerGroupCommand$ConsumerGroupService$class.describePartitions(ConsumerGroupCommand.scala:328)\nat kafka.admin.ConsumerGroupCommand$ConsumerGroupService$class.collectConsumerAssignment(ConsumerGroupCommand.scala:308)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService.collectConsumerAssignment(ConsumerGroupCommand.scala:544)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService$$anonfun$10$$anonfun$13.apply(ConsumerGroupCommand.scala:571)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService$$anonfun$10$$anonfun$13.apply(ConsumerGroupCommand.scala:565)\nat scala.collection.immutable.List.flatMap(List.scala:338)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService$$anonfun$10.apply(ConsumerGroupCommand.scala:565)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService$$anonfun$10.apply(ConsumerGroupCommand.scala:558)\nat scala.Option.map(Option.scala:146)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService.collectGroupOffsets(ConsumerGroupCommand.scala:558)\nat kafka.admin.ConsumerGroupCommand$ConsumerGroupService$class.describeGroup(ConsumerGroupCommand.scala:271)\nat kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService.describeGroup(ConsumerGroupCommand.scala:544)\nat kafka.admin.ConsumerGroupCommand$.main(ConsumerGroupCommand.scala:77)\nat kafka.admin.ConsumerGroupCommand.main(ConsumerGroupCommand.scala)\n[2018-06-12 01:32:34,255] DEBUG Removed sensor with name connections-closed: (org.apache.kafka.common.metrics.Metrics)", "branch": "1.1.0", "issue_url": "https://issues.apache.org/jira/browse/KAFKA-7044", "fix_url": "https://github.com/apache/kafka/pull/5627", "issue_created": "2018-06-12", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "kafka-8289", "system": "kafka", "issue_number": "8289", "lite": true, "title": "KTable, Long> can't be suppressed", "description": "I write a simple stream app followed official developer guide Stream DSL. but I got more than one Window Final Results from a session time window.\n\ntime ticker A -> (4,A) / 25s,\n\ntime ticker B -> (4, B) / 25s all send to the same topic \n\nbelow is my stream app code \n\nkstreams[0]\n.peek((k, v) -> log.info(\"--> ping, k={},v={}\", k, v))\n.groupBy((k, v) -> v, Grouped.with(Serdes.String(), Serdes.String()))\n.windowedBy(SessionWindows.with(Duration.ofSeconds(100)).grace(Duration.ofMillis(20)))\n.count()\n.suppress(Suppressed.untilWindowCloses(BufferConfig.unbounded()))\n.toStream().peek((k, v) -> log.info(\"window={},k={},v={}\", k.window(), k.key(), v));\nhere is my log print\n\n2019-04-24 20:00:26.142 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:00:47.070 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556106587744, endMs=1556107129191},k=A,v=20\n2019-04-24 20:00:51.071 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:01:16.065 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:01:41.066 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:02:06.069 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:02:31.066 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:02:56.208 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:03:21.070 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:03:46.078 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:04:04.684 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:04:11.069 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:04:19.371 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107426409},k=B,v=9\n2019-04-24 20:04:19.372 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107445012},k=A,v=1\n2019-04-24 20:04:29.604 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:04:36.067 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:04:49.715 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107451397},k=B,v=10\n2019-04-24 20:04:49.716 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107469935},k=A,v=2\n2019-04-24 20:04:54.593 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:05:01.070 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:05:19.599 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:05:20.045 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107476398},k=B,v=11\n2019-04-24 20:05:20.047 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107501398},k=B,v=12\n2019-04-24 20:05:26.075 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:05:44.598 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:05:50.399 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107519930},k=A,v=4\n2019-04-24 20:05:50.400 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107526405},k=B,v=13\n2019-04-24 20:05:51.067 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:06:09.595 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:06:16.089 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:06:20.765 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107544929},k=A,v=5\n2019-04-24 20:06:20.767 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107569926},k=A,v=6\n2019-04-24 20:06:34.595 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:06:41.063 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:06:51.081 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107576415},k=B,v=15\n2019-04-24 20:06:51.082 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107594925},k=A,v=7\n2019-04-24 20:06:59.607 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:07:06.072 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:07:21.440 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107601391},k=B,v=16\n2019-04-24 20:07:21.441 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107619935},k=A,v=8\n2019-04-24 20:07:24.596 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:07:31.066 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:07:49.608 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:07:51.775 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107626420},k=B,v=17\n2019-04-24 20:07:51.777 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107651396},k=B,v=18\n2019-04-24 20:07:56.064 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:08:14.591 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:08:21.066 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:08:22.125 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107669943},k=A,v=10\n2019-04-24 20:08:22.126 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107694921},k=A,v=11\n2019-04-24 20:08:39.619 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:08:46.067 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:08:52.457 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107701397},k=B,v=20\n2019-04-24 20:08:52.458 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107719949},k=A,v=12\n2019-04-24 20:09:04.599 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=A\n2019-04-24 20:09:11.066 INFO --- [-StreamThread-1] c.g.k.AppStreams : --> ping, k=4,v=B\n2019-04-24 20:09:22.794 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107226473, endMs=1556107726398},k=B,v=21 \n2019-04-24 20:09:22.796 INFO --- [-StreamThread-1] c.g.k.AppStreams : window=Window{startMs=1556107445012, endMs=1556107744928},k=A,v=13\n Can‘t a [SessionWindowedKStream] be suppressed after count operation? It seems the latest type record produce a previous type record 'Window Final Results'. I just want get exactly one Window Final Results. \n\nFirst i just start one time ticker, log print seems ok, when I start the second, then window info print log appeared.\n\nMy source stream record rate is a same v record / 25s, gap of inactivity is 100s, 25<100. I shouldn't got so many window info print log. Session window close and then reopened? my grace is 20 millisecond, it should not be ah. ", "branch": "2.2.0", "issue_url": "https://issues.apache.org/jira/browse/KAFKA-8289", "fix_url": "https://github.com/apache/kafka/pull/6654", "issue_created": "2019-04-25", "severity": "Blocker", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kafka-8950", "system": "kafka", "issue_number": "8950", "lite": true, "title": "KafkaConsumer stops fetching", "description": "We have a KafkaConsumer consuming from a single partition with enable.auto.commit set to true.\n\nVery occasionally, the consumer goes into a broken state. It returns no records from the broker with every poll, and from most of the Kafka metrics in the consumer it looks like it is fully caught up to the end of the log. \n\nWe see that we are long polling for the max poll timeout, and that there is zero lag. In addition, we see that the heartbeat rate stays unchanged from before the issue begins (so the consumer stays a part of the consumer group).\n\nIn addition, from looking at the __consumer_offsets topic, it is possible to see that the consumer is committing the same offset on the auto commit interval, however, the offset does not move, and the lag from the broker's perspective continues to increase.\n\nThe issue is only resolved by restarting our application (which restarts the KafkaConsumer instance).\n\nFrom a heap dump of an application in this state, I can see that the Fetcher is in a state where it believes there are nodesWithPendingFetchRequests.\n\nHowever, I can see the state of the fetch latency sensor, specifically, the fetch rate, and see that the samples were not updated for a long period of time (actually, precisely the amount of time that the problem in our application was occurring, around 50 hours - we have alerting on other metrics but not the fetch rate, so we didn't notice the problem until a customer complained).\n\nIn this example, the consumer was processing around 40 messages per second, with an average size of about 10kb, although most of the other examples of this have happened with higher volume (250 messages / second, around 23kb per message on average).\n\nI have spent some time investigating the issue on our end, and will continue to do so as time allows, however I wanted to raise this as an issue because it may be affecting other people.\n\nPlease let me know if you have any questions or need additional information. I doubt I can provide heap dumps unfortunately, but I can provide further information as needed.", "branch": "2.3.0", "issue_url": "https://issues.apache.org/jira/browse/KAFKA-8950", "fix_url": "https://github.com/apache/kafka/pull/7511", "issue_created": "2019-09-26", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kafka-13407", "system": "kafka", "issue_number": "13407", "lite": true, "title": "Kafka controller out of service after ZK leader restart", "description": "When the Zookeeper leader disappears, a new instance becomes the leader, the instances need to reconnect to Zookeeper, but the Kafka \"Controller\" gets lost in limbo state after re-establishing connection.\n\nSee below for how I manage to reproduce this over and over.\n\nPrerequisites\n\nHave a Kafka cluster with 3 instances running version 2.8.1. Figure out which one is the Controller. I'm using Kafkacat 1.5.0 and get this info using the `-L` flag.\n\nZookeeper runs with 3 instances on version 3.5.9. Figure out which one is leader by checking\n\n \n\necho stat | nc -v localhost 2181\n \n\n \n\nReproduce\n\n1. Stop the leader Zookeeper service.\n\n2. Watch the logs of the Kafka Controller and ensure that it reconnects and registers again.\n\n \n\nOct 27 09:13:08 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:08,882] INFO Unable to read additional data from server sessionid 0x1f2a12870003, likely server has closed socket, closing socket connection and attempting reconnect (org.apache.zookeeper.ClientCnxn)\nOct 27 09:13:10 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:10,548] WARN SASL configuration failed: javax.security.auth.login.LoginException: No JAAS configuration section named 'Client' was found in specified JAAS configuration file: '/opt/kafka/config/kafka_server_jaas.conf'. Will continue connection to Zookeeper server without SASL authentication, if Zookeeper server allows it. (org.apache.zookeeper.ClientCnxn)\nOct 27 09:13:10 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:10,548] INFO Opening socket connection to server zookeeper-kafka.service.consul.lab.aws.blue.example.net/10.10.84.12:2181 (org.apache.zookeeper.ClientCnxn)\nOct 27 09:13:10 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:10,548] ERROR [ZooKeeperClient Kafka server] Auth failed. (kafka.zookeeper.ZooKeeperClient)\nOct 27 09:13:10 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:10,549] INFO Socket connection established, initiating session, client: /10.10.85.215:39338, server: zookeeper-kafka.service.consul.lab.aws.blue.example.net/10.10.84.12:2181 (org.apache.zookeeper.ClientCnxn)\nOct 27 09:13:10 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:10,569] INFO Session establishment complete on server zookeeper-kafka.service.consul.lab.aws.blue.example.net/10.10.84.12:2181, sessionid = 0x1f2a12870003, negotiated timeout = 18000 (org.apache.zookeeper.ClientCnxn)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,548] INFO [ZooKeeperClient Kafka server] Reinitializing due to auth failure. (kafka.zookeeper.ZooKeeperClient)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,550] INFO [PartitionStateMachine controllerId=1003] Stopped partition state machine (kafka.controller.ZkPartitionStateMachine)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,550] INFO [ReplicaStateMachine controllerId=1003] Stopped replica state machine (kafka.controller.ZkReplicaStateMachine)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,551] INFO [RequestSendThread controllerId=1003] Shutting down (kafka.controller.RequestSendThread)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,551] INFO [RequestSendThread controllerId=1003] Stopped (kafka.controller.RequestSendThread)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,551] INFO [RequestSendThread controllerId=1003] Shutdown completed (kafka.controller.RequestSendThread)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,552] INFO [RequestSendThread controllerId=1003] Shutting down (kafka.controller.RequestSendThread)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,552] INFO [RequestSendThread controllerId=1003] Stopped (kafka.controller.RequestSendThread)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,552] INFO [RequestSendThread controllerId=1003] Shutdown completed (kafka.controller.RequestSendThread)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,554] INFO [RequestSendThread controllerId=1003] Shutting down (kafka.controller.RequestSendThread)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,554] INFO [RequestSendThread controllerId=1003] Stopped (kafka.controller.RequestSendThread)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,554] INFO [RequestSendThread controllerId=1003] Shutdown completed (kafka.controller.RequestSendThread)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,556] INFO Processing notification(s) to /config/changes (kafka.common.ZkNodeChangeNotificationListener)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,557] INFO [Controller id=1003] Resigned (kafka.controller.KafkaController)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,557] INFO Creating /brokers/ids/1003 (is it secure? false) (kafka.zk.KafkaZkClient)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,560] INFO Updated cache from existing FinalizedFeaturesAndEpoch(features=Features{}, epoch=1) to latest FinalizedFeaturesAndEpoch(features=Features{}, epoch=1). (kafka.server.FinalizedFeatureCache)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,572] INFO Stat of the created znode at /brokers/ids/1003 is: 128849019044,128849019044,1635323000996,1635323000996,1,0,0,34265559924739,389,0,128849019044\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: (kafka.zk.KafkaZkClient)\nOct 27 09:13:11 ip-10-10-85-215 kafka[62961]: [2021-10-27 09:13:11,572] INFO Registered broker 1003 at path /brokers/ids/1003 with addresses: PLAINTEXT://kafka-tr-2.node.consul.lab.aws.blue.example.net:9093,SASL_SSL://kafka-tr-2.node.consul.lab.aws.blue.example.net:9092, czxid (broker epoch): 128849019044 (kafka.zk.KafkaZkClient)\n \n\n \n\nNow it is in this limbo state but to notice the problem create a topic for example.\n\n \n\n./kafka-topics.sh --zookeeper zookeeper-kafka.service.consul.lab.aws.blue.example.net:2181/kafka_tr --create --topic danols-ts-4 --partitions 10 --replication-factor 3\nCreated topic danols-ts-4.\n \n\n \n\nThen when describing the topic it looks like this:\n\n \n\n./kafka-topics.sh --zookeeper zookeeper-kafka.service.consul.lab.aws.blue.example.net:2181/kafka_tr --describe --topic danols-ts-4\nTopic: danols-ts-4 PartitionCount: 10 ReplicationFactor: 3 Configs: \n Topic: danols-ts-4 Partition: 0 Leader: none Replicas: 1003,1001,1002 Isr: \n Topic: danols-ts-4 Partition: 1 Leader: none Replicas: 1001,1002,1003 Isr: \n Topic: danols-ts-4 Partition: 2 Leader: none Replicas: 1002,1003,1001 Isr: \n Topic: danols-ts-4 Partition: 3 Leader: none Replicas: 1003,1002,1001 Isr: \n Topic: danols-ts-4 Partition: 4 Leader: none Replicas: 1001,1003,1002 Isr: \n Topic: danols-ts-4 Partition: 5 Leader: none Replicas: 1002,1001,1003 Isr: \n Topic: danols-ts-4 Partition: 6 Leader: none Replicas: 1003,1001,1002 Isr: \n Topic: danols-ts-4 Partition: 7 Leader: none Replicas: 1001,1002,1003 Isr: \n Topic: danols-ts-4 Partition: 8 Leader: none Replicas: 1002,1003,1001 Isr: \n Topic: danols-ts-4 Partition: 9 Leader: none Replicas: 1003,1002,1001 Isr: \n\n \n\n \n\nIf I describe using the --bootstrap-server flag instead it doesn't exist\n\n./kafka-topics.sh --bootstrap-server localhost:9093 --describe --topic danols-ts-4\nError while executing topic command : Topic 'danols-ts-4' does not exist as expected\n[2021-10-27 09:24:15,691] ERROR java.lang.IllegalArgumentException: Topic 'danols-ts-4' does not exist as expected\n at kafka.admin.TopicCommand$.kafka$admin$TopicCommand$$ensureTopicExists(TopicCommand.scala:542)\n at kafka.admin.TopicCommand$AdminClientTopicService.describeTopic(TopicCommand.scala:317)\n at kafka.admin.TopicCommand$.main(TopicCommand.scala:69)\n at kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)\nIf I restart the Kafka service on a broker that is not \"Controller\" it doesn't come up again. It just spams the following in the log for all different partitions and it's not possible to connect to it.\n\nOct 27 09:27:48 ip-10-226-69-122 kafka[67342]: org.apache.kafka.common.errors.InvalidReplicationFactorException: Replication factor: 3 larger than available brokers: 0.\nOct 27 09:27:48 ip-10-226-69-122 kafka[67342]: [2021-10-27 09:27:48,984] INFO [Admin Manager on Broker 1001]: Error processing create topic request CreatableTopic(name='example-message-consumer', numPartitions=10, replicationFactor=3, assignments=[], configs=[]) (kafka.server.ZkAdminManager)\nOct 27 09:27:48 ip-10-226-69-122 kafka[67342]: org.apache.kafka.common.errors.InvalidReplicationFactorException: Replication factor: 3 larger than available brokers: 0.\nOct 27 09:27:49 ip-10-226-69-122 kafka[67342]: [2021-10-27 09:27:49,021] INFO [Admin Manager on Broker 1001]: Error processing create topic request CreatableTopic(name='__consumer_offsets', numPartitions=50, replicationFactor=3, assignments=[], configs=[CreateableTopicConfig(name='compression.type', value='producer'), CreateableTopicConfig(name='cleanup.policy', value='compact'), CreateableTopicConfig(name='segment.bytes', value='104857600')]) (kafka.server.ZkAdminManager)\nTo get out of this state I simply restart the Kafka service on the \"Controller\". It will make another become \"Controller\" and all brokers becomes OK again and the newly created topic gets all expected ISRs.", "branch": "2.8.1", "issue_url": "https://issues.apache.org/jira/browse/KAFKA-13407", "fix_url": "https://github.com/apache/kafka/pull/11563/files", "issue_created": "2021-10-27", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "kafka-13668", "system": "kafka", "issue_number": "13668", "lite": true, "title": "Failed cluster authorization should not be fatal for producer", "description": "The idempotent producer fails fatally if the initial `InitProducerId` returns CLUSTER_AUTHORIZATION_FAILED. This makes the producer unusable until a new instance is constructed. For some applications, it is more convenient to keep the producer instance active and let the administrator fix the permission problem instead of going into a crash loop. Additionally, most applications will probably not be smart enough to reconstruct the producer instance, so if the application does not handle the error by failing, users will have to restart the application manually. \n\nI think it would be better to let the producer retry the `InitProducerId` request as long as the user keeps trying to use the producer. ", "branch": "3.5.1", "issue_url": "https://issues.apache.org/jira/browse/KAFKA-13668", "fix_url": "https://github.com/apache/kafka/pull/12149/files", "issue_created": "2022-02-15", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": false, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kafka-17062", "system": "kafka", "issue_number": "17062", "lite": true, "title": "RemoteLogManager - RemoteStorageException causes data loss", "description": "When Tiered Storage is configured, retention.bytes defines the limit for the amount of data stored in the filesystem and in remote storage. However a failure while offloading to remote storage can cause segments to be dropped before the retention limit is met.\n\nWhat happens\n\nAssuming a topic configured with retention.bytes=4294967296 (4GB) and a local.retention.bytes=1073741824 (1GB, equal to segment.bytes) we would expect Kafka to keep up to 3 segments (3GB) in the remote store and 1 segment locally (the local segment) and possibly more if the remote storage is offline. i.e. segments in the following RemoteLogSegmentStates in the RemoteLogMetadataManager (RLMM) :\n\nSegment 3 (COPY_SEGMENT_FINISHED)\nSegment 2 (COPY_SEGMENT_FINISHED)\nSegment 1 (COPY_SEGMENT_FINISHED)\nLet's assume the RLMM starts failing when segment 4 rolls. At the first iteration of an RLMTask we will have -\n\ncopyLogSegmentsToRemote : is called first\nRLMM becomes aware of Segment 4 and adds it to the metadata:\nSegment 4 (COPY_SEGMENT_STARTED),\nSegment 3 (COPY_SEGMENT_FINISHED),\nSegment 2 (COPY_SEGMENT_FINISHED),\nSegment 1 (COPY_SEGMENT_FINISHED)\nAn exception is raised during the copy operation (copyLogSegmentData in RemoteStorageManager) which is caught with the error message “Error occurred while copying log segments of partition” and no further copy will be attempted for the duration of this RLMTask.\nAt that point the Segment will never move to COPY_SEGMENT_FINISHED but will transition to DELETE_SEGMENT_STARTED eventually before being cleaned up when the associated segment is deleted.\ncleanupExpiredRemoteLogSegments is then called\nRetention size is computed in buildRetentionSizeData as the sum of all the segments size regardless of their state so computed size of the topic is 1 (local) + 4 (remote)\nSegment 1 as being the oldest will be dropped.\nAt the second iteration after remote.log.manager.task.interval.ms (default: 30s), the same will happen. The RLMM will now have 2 x Segment 4 in a COPY_SEGMENT_STARTED state each with a different RemoteLogSegmentId and Segment 2 will be dropped. The same will happen to Segment 3 after another iteration.\n\nAt that point, we now have the RLMM composed of 4 copies of Segment 4 in COPY_SEGMENT_STARTED state. Segment 4 is marked for deletion increasing the LSO at the same time and causing the UnifiedLog to delete the local and remote data for Segment 4 including its metadata.\n\nUnder those circumstances Kafka can quickly delete segments that were not meant for deletion causing a data loss.\n\nSteps to reproduce the problem:\n\n1. Enable tiered storage\n\nmkdir -p /tmp/tieredStorage/kafka-tiered-storage/\ncat <> config/kraft/server.properties\nremote.log.storage.system.enable=True\nremote.log.storage.manager.class.name=org.apache.kafka.server.log.remote.storage.LocalTieredStorage\nremote.log.manager.task.interval.ms=5000\nremote.log.metadata.manager.listener.name=PLAINTEXT\nrlmm.config.remote.log.metadata.topic.replication.factor=1\nrsm.config.dir=/tmp/tieredStorage\nEOF\n2. Start a Kafka server with the following classpath. This is needed so we can use test class LocalTieredStorage as an implementation of RemoteStorageManager.\n\nexport CLASSPATH=\"$(pwd)/storage/build/libs/{*}:$(pwd)/clients/build/libs/{*}\"\nexport KAFKA_CLUSTER_ID=\"$(bin/kafka-storage.sh random-uuid)\"\nbin/kafka-storage.sh format -t $KAFKA_CLUSTER_ID -c config/kraft/server.properties\nbin/kafka-server-start.sh config/kraft/server.properties\n3. In a separate shell, create the topic and produce enough records to fill the remote log\n\nbin/kafka-topics.sh --create --topic bug-ts --bootstrap-server localhost:9092 \\\n --config retention.bytes=1000000000 --config segment.bytes=100000000 \\\n --config remote.storage.enable=true --config local.retention.bytes=1\nbin/kafka-producer-perf-test.sh --topic bug-ts --num-records=1000000 \\\n --throughput -1 --record-size 1000 \\\n --producer-props acks=1 batch.size=100000 bootstrap.servers=localhost:9092\n4. In a separate shell, watch the remote log directory content\n\nwatch -n 1 – s -R /tmp/tieredStorage/kafka-tiered-storage/\n5. Once all logs are sent to the remote storage (when the server logs stops, should take around 2min), stop the Kafka server\n6. Edit the file LocalTieredStorage#L309 in copyLogSegmentData() in order to throw a RemoteStorageException and disable the ability to store new remote segments.\n7. Rebuild Kafka\n\n ./gradlew testJar\n8. Restart the Kafka server\n\nbin/kafka-server-start.sh config/kraft/server.properties\n9. Send enough data for one segment rollup\n\nbin/kafka-producer-perf-test.sh \\\n --topic bug-ts --num-records=10000 --throughput -1 --record-size 10000 \\\n --producer-props acks=1 batch.size=100000 bootstrap.servers=localhost:9092\nAll data in the remote directory will start getting deleted when we would expect just no more writes to happen to the remote storage.", "branch": "3.8.0", "issue_url": "https://issues.apache.org/jira/browse/KAFKA-17062", "fix_url": "https://github.com/apache/kafka/pull/16959", "issue_created": "2024-07-02", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kafka-18073", "system": "kafka", "issue_number": "18073", "lite": true, "title": "Data loss when exception is raised from Kafka Connect record conversion call", "description": "We are experiencing data loss when Kafka Connect source connector fails to send data to Kafka topic after receiving a retriable exception from a schema registry (when converting the record).\n\nKafka cluster & connect details:\n\nKafka Connect version: 3.8.1\nKafka Version 3.6.1\nCluster size: 16 brokers\nNumber of partitions in Kafka data topic: 32\nNumber of partitions in offsets topic: \nReplication Factor: 4\nMin In Sync Replicas: 2\nUnclean leader election disabled\nUses Apicurio schema registry to convert to Avro\nUses default error tolerance i.e., None\nProducer configs\n\nacks = -1\nmax.in.flight.requests.per.connection = 1\nbatch.size = 524288\nOur connector uses the offsets committed by Kafka Connect (does not have any internal checkpointing/state storage).\n\nData loss is noticed on occasion when a timeout is received during the convertTransformedRecod call. The timeout is from connecting to the schema registry for the schema. Full stack trace here\n\nLogs (dropped record is from task 79):\n\n2024-10-22T01:37:41.059Z - INFO - WorkerSourceTask{id=keyspace1-connector-79} Committing offsets for 3 acknowledged messages\n2024-10-22T01:37:41.066Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-232} Committing offsets for 1 acknowledged messages\n2024-10-22T01:37:41.540Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-259} Committing offsets for 3 acknowledged messages\n2024-10-22T01:37:41.928Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-273} Committing offsets for 2 acknowledged messages\n2024-10-22T01:37:44Z - info - Handshake message sent\n2024-10-22T01:37:51Z - info - Handshake timed out\n2024-10-22T01:37:52Z - info - Handshake message sent\n2024-10-22T01:37:58Z - info - Handshake timed out\n2024-10-22T01:38:04Z - info - Handshake message sent\n2024-10-22T01:38:10Z - info - Handshake timed out\n2024-10-22T01:38:11.664Z - INFO - [Producer clientId=connector-producer-keyspace1-table1-connector-268] Node 1078 disconnected.\n2024-10-22T01:38:15.798Z - INFO - [Producer clientId=connector-producer-keyspace1-table1-connector-219] Node 1089 disconnected.\n2024-10-22T01:38:20Z - info - Handshake message sent\n2024-10-22T01:38:23.225Z - INFO - [Producer clientId=connector-producer-keyspace1-connector-107] Node 1085 disconnected.\n2024-10-22T01:38:23.224Z - INFO - [Producer clientId=connector-producer-keyspace1-connector-107] Node 1088 disconnected.\n2024-10-22T01:38:24.536Z - INFO - [Producer clientId=connector-producer-keyspace1-table1-connector-13] Node 1076 disconnected.\n2024-10-22T01:38:27Z - info - Handshake timed out\n2024-10-22T01:38:27.491Z - INFO - [Producer clientId=connector-producer-keyspace1-table1-connector-237] Node 1082 disconnected.\n2024-10-22T01:38:27.492Z - INFO - [Producer clientId=connector-producer-keyspace1-table1-connector-237] Node 1089 disconnected.\n2024-10-22T01:38:27.493Z - INFO - [Producer clientId=connector-producer-keyspace1-table1-connector-237] Node 1085 disconnected.\n2024-10-22T01:38:27.832Z - INFO - [Producer clientId=connector-producer-keyspace1-table1-connector-237] Node 1088 disconnected.\n2024-10-22T01:38:28.470Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-12} Committing offsets for 2 acknowledged messages\n2024-10-22T01:38:28.549Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-64} Committing offsets for 14 acknowledged messages\n2024-10-22T01:38:36.930Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-53} Committing offsets for 38 acknowledged messages\n2024-10-22T01:38:37.701Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-13} Committing offsets for 2 acknowledged messages\n2024-10-22T01:38:37.838Z - INFO - [AdminClient clientId=dbzium-prod-keyspace1-shared-admin] Node 1089 disconnected.\n2024-10-22T01:38:38.369Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-25} Committing offsets for 6 acknowledged messages\n2024-10-22T01:38:39.212Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-56} Committing offsets for 21 acknowledged messages\n2024-10-22T01:38:39.597Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-51} Committing offsets for 11 acknowledged messages\n2024-10-22T01:38:39.642Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-219} Committing offsets for 4 acknowledged messages\n2024-10-22T01:38:39.647Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-237} Committing offsets for 1 acknowledged messages\n2024-10-22T01:38:39.681Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-268} Committing offsets for 8 acknowledged messages\n2024-10-22T01:38:41.059Z - INFO - WorkerSourceTask{id=keyspace1-connector-107} Committing offsets for 3 acknowledged messages\n2024-10-22T01:38:41.540Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-232} Committing offsets for 3 acknowledged messages\n2024-10-22T01:38:41.928Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-259} Committing offsets for 2 acknowledged messages\n2024-10-22T01:38:42.252Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-273} Committing offsets for 1 acknowledged messages\n2024-10-22T01:38:44.913Z - ERROR - Failed to send HTTP request to endpoint: http://schema-registry.service.prod-us-east-1-dw1.consul:8080/apis/ccompat/v6/subjects/prod.keyspace1.table1-key/versions?normalize=false\n2024-10-22T01:38:52Z - info - Handshake message sent\n2024-10-22T01:39:06.790Z - INFO - [Worker clientId=connect-dbzium-prod-keyspace1-b7cfc9bcc-8z59m.node.prod-us-east-1-vitess1.consul:8083, groupId=dbzium-prod-keyspace1] Rebalance started\n2024-10-22T01:39:07.134Z - INFO - [Worker clientId=connect-dbzium-prod-keyspace1-b7cfc9bcc-8z59m.node.prod-us-east-1-vitess1.consul:8083, groupId=dbzium-prod-keyspace1] Successfully joined group with generation Generation{generationId=2477, memberId='connect-dbzium-prod-keyspace1-b7cfc9bcc-8z59m.node.prod-us-east-1-vitess1.consul:8083-a174acf5-1b8f-419a-a25a-4c58dab02a8d', protocol='sessioned'}\n2024-10-22T01:39:07.171Z - INFO - [Worker clientId=connect-dbzium-prod-keyspace1-b7cfc9bcc-8z59m.node.prod-us-east-1-vitess1.consul:8083, groupId=dbzium-prod-keyspace1] Successfully synced group in generation Generation{generationId=2477, memberId='connect-dbzium-prod-keyspace1-b7cfc9bcc-8z59m.node.prod-us-east-1-vitess1.consul:8083-a174acf5-1b8f-419a-a25a-4c58dab02a8d', protocol='sessioned'}\n2024-10-22T01:39:07.171Z - INFO - [Worker clientId=connect-dbzium-prod-keyspace1-b7cfc9bcc-8z59m.node.prod-us-east-1-vitess1.consul:8083, groupId=dbzium-prod-keyspace1] Joined group at generation 2477 with protocol version 2 and got assignment: Assignment{error=0, leader='connect-dbzium-prod-keyspace1-b7cfc9bcc-h8gxb.node.prod-us-east-1-vitess1.consul:8083-dbbc75cb-1de9-4907-bf4c-f3f6cca6eb9a', leaderUrl='http://dbzium-prod-keyspace1-b7cfc9bcc-h8gxb.node.prod-us-east-1-vitess1.consul:8083/', offset=236838, connectorIds=[], taskIds=[keyspace1-table1-connector-12, keyspace1-table1-connector-13, keyspace1-table1-connector-25, keyspace1-table1-connector-51, keyspace1-table1-connector-53, keyspace1-table1-connector-56, keyspace1-table1-connector-64, keyspace1-table1-connector-219, keyspace1-table1-connector-232, keyspace1-table1-connector-237, keyspace1-table1-connector-259, keyspace1-table1-connector-268, keyspace1-table1-connector-273, keyspace1-connector-79, keyspace1-connector-107, keyspace1-connector-285], revokedConnectorIds=[], revokedTaskIds=[], delay=180000} with rebalance delay: 180000\n2024-10-22T01:39:07.172Z - INFO - [Worker clientId=connect-dbzium-prod-keyspace1-b7cfc9bcc-8z59m.node.prod-us-east-1-vitess1.consul:8083, groupId=dbzium-prod-keyspace1] Finished starting connectors and tasks\n2024-10-22T01:39:07.172Z - INFO - [Worker clientId=connect-dbzium-prod-keyspace1-b7cfc9bcc-8z59m.node.prod-us-east-1-vitess1.consul:8083, groupId=dbzium-prod-keyspace1] Starting connectors and tasks using config offset 236838\n2024-10-22T01:39:12Z - info - Handshake message received\n2024-10-22T01:39:12Z - info - Handshake message sent\n2024-10-22T01:39:27.534Z - INFO - [Producer clientId=connector-producer-keyspace1-connector-107] Node 1074 disconnected.\n2024-10-22T01:39:27.535Z - INFO - [Producer clientId=connector-producer-keyspace1-connector-107] Node 1077 disconnected.\n2024-10-22T01:39:28.550Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-12} Committing offsets for 4 acknowledged messages\n2024-10-22T01:39:28.622Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-64} Committing offsets for 48 acknowledged messages\n2024-10-22T01:39:37.102Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-53} Committing offsets for 30 acknowledged messages\n2024-10-22T01:39:38.194Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-13} Committing offsets for 3 acknowledged messages\n2024-10-22T01:39:38.556Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-25} Committing offsets for 14 acknowledged messages\n2024-10-22T01:39:39.598Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-56} Committing offsets for 15 acknowledged messages\n2024-10-22T01:39:40.043Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-51} Committing offsets for 8 acknowledged messages\n2024-10-22T01:39:40.086Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-219} Committing offsets for 6 acknowledged messages\n2024-10-22T01:39:40.096Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-237} Committing offsets for 1 acknowledged messages\n2024-10-22T01:39:40.100Z - INFO - WorkerSourceTask{id=keyspace1-table1-connector-268} Committing offsets for 8 acknowledged messages\n2024-10-22T01:39:41.392Z - INFO - WorkerSourceTask{id=keyspace1-connector-79} Committing offsets for 12 acknowledged messages\nDoes Kafka Connect commit offsets for a batch even if some of the records failed? Or must the whole batch be successful to commit offsets?\n\nIt is odd there is no restart, just a logged error that should have been retried.", "branch": "3.1.0", "issue_url": "https://issues.apache.org/jira/browse/KAFKA-18073", "fix_url": "https://github.com/apache/kafka/pull/18146", "issue_created": "2024-11-23", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-135981", "system": "kubernetes", "issue_number": "135981", "lite": true, "title": "scheduler_unschedulable_pods metric might broke when running PreEnqueue plugins", "description": "What happened?\nscheduler_unschedulable_pods metric stores the number of unschedulable pods broken down by plugin name. It is incremented when the pod is re-added to the scheduling queue (with its all unschedulable and pending plugins) as well as when PreEnqueue plugin fails for such pod. When the pod is popped out from the scheduling queue, the metric is decremented using pod's unschedulable and pending pods lists. However, if PreEnqueue fails for a plugin that was already reported as unschedulable for a pod, the metric is still incremented (multiple ones for one plugin and one pod) what leads to not clearing the metric properly when popping out the pod.\n\nWhat did you expect to happen?\nscheduler_unschedulable_pods metric to be incremented properly when PreEnqueue fails.\n\nHow can we reproduce it (as minimally and precisely as possible)?\nCreate a pod that will get rejected by a plugin while scheduling (e.g. on Filter) and then blocked by PreEnqueue by the same plugin. If the pod is finally scheduled, the scheduler_unschedulable_pods will be non-zero.", "branch": "0ba578f91f5", "issue_url": "https://github.com/kubernetes/kubernetes/issues/132333", "fix_url": "https://github.com/kubernetes/kubernetes/pull/135981", "issue_created": null, "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-135983", "system": "kubernetes", "issue_number": "135983", "lite": false, "title": "Slow pod scheduling when ResourceClaimTemplate is created after pod creation due to exponential backoff", "description": "What happened?\nWhen a Pod references a ResourceClaimTemplate (RCT) that doesn't exist at pod creation time, and the RCT is created later, there can be significant delays before the pod gets scheduled.\n\nRoot Cause:\n\nThe ResourceClaim controller in kube-controller-manager uses AddRateLimited() when the referenced ResourceClaimTemplate is not found. This applies dual rate limiting:\n\nExponential backoff (per-item): 5ms × 2^failures, capped at 1000 seconds\nToken bucket (global): 10 QPS with 100-token burst\nThe final delay is MAX(exponential_delay, token_bucket_delay).\n\nThe Problem:\n\nWhen the ResourceClaimTemplate is eventually created, there is no mechanism to:\n\nNotify the ResourceClaim controller to immediately reprocess waiting pods\nMove affected pods from unschedulablePods queue back to activeQ in the scheduler\nThe pod must wait for its current backoff period to expire before the controller retries, which can be up to 1000 seconds if the pod has already failed multiple times.\n\nWhat did you expect to happen?\nWhen a new ResourceClaimTemplate is created, pods that were waiting due to the missing template should be processed promptly (within seconds), not after potentially long backoff delays.\n\nHow to reproduce it (as minimally and precisely as possible)?\nCreate a Pod that references a non-existent ResourceClaimTemplate:\napiVersion: v1\nkind: Pod\nmetadata:\n name: test-pod\nspec:\n containers:\n - name: test\n image: nginx\n resources:\n claims:\n - name: my-claim\n resourceClaims:\n - name: my-claim\n resourceClaimTemplateName: my-template # Does not exist yet\nWait for several retry cycles (observe increasing backoff delays in controller logs)\nCreate the ResourceClaimTemplate:\napiVersion: resource.k8s.io/v1\nkind: ResourceClaimTemplate\nmetadata:\n name: my-template\nspec:\n spec:\n devices:\n requests:\n - name: device\n deviceClassName: example-class", "branch": "4e69edd0eea", "issue_url": "https://github.com/kubernetes/kubernetes/issues/135835", "fix_url": "https://github.com/kubernetes/kubernetes/pull/135983", "issue_created": null, "severity": "Major", "root_cause_type": "Communication", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-136014", "system": "kubernetes", "issue_number": "136014", "lite": false, "title": "kubeadm should confirm that the new etcd peer has started before trying to promote it to a member, and even remove the unstarted peer", "description": "What would you like to be added?\nI think kubeadm should confirm that the new etcd peer has started. If it is has not (e.g. because the etcd image is unavailable, or kubelet has stopped), then kubeadm should not try to promote it to a member, and should eventually remove the member.\n\nWhy is this needed?\nWhen kubeadm joins a control plane node with local etcd, it\n\nMakes an etcd API call to add a new etcd peer as a learner.\nCreates the etcd static pod\nMakes an API call to promote the learner to a member\nFor (3) to complete, the etcd peer must be started.\n\nIf it is not started, then (3) eventually fails, and kubeadm just returns the etcd API call error: can only promote a learner member which is in sync with leader. This error is ambiguous, because it can have other causes, like poor disk/network performance.\n\nMoreover, if the etcd peer never started, then it can safely be removed from the membership list, and kubeadm should do that.", "branch": "1c9180cd453", "issue_url": "https://github.com/kubernetes/kubeadm/issues/3269", "fix_url": "https://github.com/kubernetes/kubernetes/pull/136014", "issue_created": null, "severity": "Major", "root_cause_type": "Communication", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-136026", "system": "kubernetes", "issue_number": "136026", "lite": false, "title": "A potential goroutine leak in pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go", "description": "What happened?\nIf the time.After case is selected before the case <-ch:\n\nkubernetes/pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go\n\nLines 164 to 175 in b6e7ee3\n\n loop: \n \tfor { \n \t\tselect { \n \t\tcase <-ch: \n \t\t\tnumOperationsStarted++ \n \t\t\tif numOperationsStarted == numOperationsToRun { \n \t\t\t\treturn true \n \t\t\t} \n \t\tcase <-time.After(5 * time.Second): \n \t\t\tbreak loop \n \t\t} \n \t} \n\nwhich leads to the ch <- nil below get blocked, results in a goroutine leak.\nkubernetes/pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go\n\nLine 188 in b6e7ee3\n\n ch <- nil \nWhat did you expect to happen?\nIf the time.After case is selected before the case <-ch:, the ch <- nil doesn't get blocked either.\n\nHow can we reproduce it (as minimally and precisely as possible)?\n1.Set time.After(5 * time.Second) to time.After(time.Millisecond * 100)\n2.Add time.Sleep(time.Millisecond * 200) before the ch <- nil\n\nkubernetes/pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go\n\nLine 188 in b6e7ee3\n\n ch <- nil \n\nThe two steps make the time.After happen before the case <-ch:.\n3.Using goleak to detect the goroutine leak in the test function\nkubernetes/pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go\n\nLine 50 in b6e7ee3\n\n func TestOperationExecutor_RegisterPlugin_ConcurrentRegisterPlugin(t *testing.T) { \nfunc TestOperationExecutor_UnregisterPlugin_ConcurrentUnregisterPlugin(t *testing.T) {\n\tdefer goleak.VerifyNone(t)\nThe error report is as follows,\n\nfound unexpected goroutines:\n [Goroutine 7 in state chan send, with k8s.io/kubernetes/pkg/kubelet/pluginmanager/operationexecutor.startOperationAndBlock on top of the stack:\n goroutine 7 [chan send]:\n k8s.io/kubernetes/pkg/kubelet/pluginmanager/operationexecutor.startOperationAndBlock(0x517d34?, 0x0?)\n \t/home/song2048/桌面/goProject/src/GoPie/testdata/realProjects/k8s.io/kubernetes/kubernetes/pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go:183 +0x4c\n k8s.io/kubernetes/pkg/kubelet/pluginmanager/operationexecutor.(*fakeOperationGenerator).GenerateUnregisterPluginFunc.func1()\n \t/home/song2048/桌面/goProject/src/GoPie/testdata/realProjects/k8s.io/kubernetes/kubernetes/pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go:124 +0x25\n k8s.io/kubernetes/pkg/util/goroutinemap.(*goRoutineMap).Run.func1()\n \t/home/song2048/桌面/goProject/src/GoPie/testdata/realProjects/k8s.io/kubernetes/kubernetes/pkg/util/goroutinemap/goroutinemap.go:119 +0xc4\n created by k8s.io/kubernetes/pkg/util/goroutinemap.(*goRoutineMap).Run\n \t/home/song2048/桌面/goProject/src/GoPie/testdata/realProjects/k8s.io/kubernetes/kubernetes/pkg/util/goroutinemap/goroutinemap.go:112 +0x4d8\n \n Goroutine 8 in state chan send, with k8s.io/kubernetes/pkg/kubelet/pluginmanager/operationexecutor.startOperationAndBlock on top of the stack:\n goroutine 8 [chan send]:\n k8s.io/kubernetes/pkg/kubelet/pluginmanager/operationexecutor.startOperationAndBlock(0x0?, 0x0?)\n \t/home/song2048/桌面/goProject/src/GoPie/testdata/realProjects/k8s.io/kubernetes/kubernetes/pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go:183 +0x4c\n k8s.io/kubernetes/pkg/kubelet/pluginmanager/operationexecutor.(*fakeOperationGenerator).GenerateUnregisterPluginFunc.func1()\n \t/home/song2048/桌面/goProject/src/GoPie/testdata/realProjects/k8s.io/kubernetes/kubernetes/pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go:124 +0x25\n k8s.io/kubernetes/pkg/util/goroutinemap.(*goRoutineMap).Run.func1()\n \t/home/song2048/桌面/goProject/src/GoPie/testdata/realProjects/k8s.io/kubernetes/kubernetes/pkg/util/goroutinemap/goroutinemap.go:119 +0xc4\n created by k8s.io/kubernetes/pkg/util/goroutinemap.(*goRoutineMap).Run\n \t/home/song2048/桌面/goProject/src/GoPie/testdata/realProjects/k8s.io/kubernetes/kubernetes/pkg/util/goroutinemap/goroutinemap.go:112 +0x4d8\n ]\n--- FAIL: TestOperationExecutor_UnregisterPlugin_ConcurrentUnregisterPlugin\nAnything else we need to know?\nHow to fix the bug:\n\nkubernetes/pkg/kubelet/pluginmanager/operationexecutor/operation_executor_test.go\n\nLine 181 in b6e7ee3\n\n ch, quit := make(chan interface{}), make(chan interface{}) \n\nChange the unbufferd channel to a buffered channel. So that the ch <- nil can't get blocked in any case.\nmake(chan interface{}, 1)", "branch": "6817bea700f", "issue_url": "https://github.com/kubernetes/kubernetes/issues/134939", "fix_url": "https://github.com/kubernetes/kubernetes/pull/136026", "issue_created": null, "severity": "Major", "root_cause_type": "Resource leak", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-136028", "system": "kubernetes", "issue_number": "136028", "lite": false, "title": "Error-level logs incorrectly use verbosity levels", "description": "Currently, some components in Kubernetes have been migrated (or partially migrated) to contextual logging. However, an incorrect pattern was introduced during the migration: Error-level logs are being called with verbosity methods (e.g., .V()).\n\nThe underlying package go-logr/logr, which contextual logging relies on, ignores the verbosity level when printing Error-level logs. For example, in the statement logger.V(8).Error(nil, \"Readiness probe already exists for container\", \"pod\", klog.KObj(pod), \"containerName\", c.Name), the error log will be printed regardless of the verbosity level set.\n\nThis can lead to error log flooding, which may hinder users' ability to review normal logs for troubleshooting. More critically, according to the Kubernetes logging policy, logs should only be recorded when the information requires action from an administrator. This directly contradicts the practice of setting verbosity levels for Error logs, as administrators using the default logging level might miss these actionable errors. Therefore, these instances need to be fixed.\n\nUsing grep, I identified the following instances in the k/k repository where verbosity levels are incorrectly set for Error logs.\n\n\n/pkg/controller/garbagecollector fix(controller/resourcequota, controller/garbagecollector): Change V().Error() to V().Info() #136040\n./pkg/controller/garbagecollector/garbagecollector.go:363:\t\t\tlogger.V(5).Error(err, \"error syncing item\", \"item\", n.identity)\n./pkg/controller/garbagecollector/graph_builder.go:225:\t\tlogger.V(4).Error(err, \"unable to use a shared informer\", \"resource\", resource, \"kind\", kind)\n\n/pkg/controller/resourcequota fix(controller/resourcequota, controller/garbagecollector): Change V().Error() to V().Info() #136040\n./pkg/controller/resourcequota/resource_quota_monitor.go:178:\tlogger.V(4).Error(err, \"QuotaMonitor unable to use a shared informer\", \"resource\", resource.String())\n\n/pkg/controller/storageversionmigrator/ fix(controller/storageversionmigrator) Reduce log level #136046\n./pkg/controller/storageversionmigrator/storageversionmigrator.go:227:\t\tlogger.V(4).Error(err, \"resource does not exist in our rest mapper\", \"gvr\", gvr.String())\n./pkg/controller/storageversionmigrator/storageversionmigrator.go:244:\t\tlogger.V(4).Error(errMonitor, \"resource does not exist in GC\", \"gvr\", gvr.String())\n./pkg/controller/storageversionmigrator/storageversionmigrator.go:311:\t\t\tlogger.V(4).Error(err, \"Unable to compare the resource version of the resource\", \"namespace\", accessor.GetNamespace(), \"name\", accessor.GetName(), \"gvr\", gvr.String(), \"accessorRV\", accessor.GetResourceVersion(), \"listResourceVersion\", listResourceVersion, \"error\", err.Error())\n./pkg/controller/storageversionmigrator/storageversionmigrator.go:361:\t\t\tlogger.V(4).Error(errPatch, \"Failed to migrate the resource\", \"namespace\", accessor.GetNamespace(), \"name\", accessor.GetName(), \"gvr\", gvr.String(), \"reason\", apierrors.ReasonForError(errPatch))\n\n./pkg/controller/volume/ fix(controller/volume): convert V().Error() to V().Info() #136050\n./pkg/controller/volume/selinuxwarning/selinux_warning_controller.go:458:\t\t\tlogger.V(4).Error(err, \"failed to get SELinux label\", \"pod\", klog.KObj(pod), \"volume\", mount)\n./pkg/controller/volume/selinuxwarning/selinux_warning_controller.go:514:\t\t\tlogger.V(2).Error(err, \"failed to get first pod for event\", \"pod\", conflict.Pod)\n\n./pkg/kubelet/volumemanager/ fix(kubelet/volumemanager): convert V().Error() to V().Info() for verbosity-aware logging #136033\n./pkg/kubelet/volumemanager/cache/desired_state_of_world.go:673:\tlogger.V(4).Error(err, \"Please report this error in https://github.com/kubernetes/enhancements/issues/1710, together with full Pod yaml file\")\n./pkg/kubelet/volumemanager/cache/desired_state_of_world.go:688:\t\tlogger.V(4).Error(err, \"failed to get CSI driver name from volume spec\")\n./pkg/kubelet/volumemanager/reconciler/reconstruct.go:188:\t\tlogger.V(4).Error(fetchErr, \"Failed to get Node status to reconstruct device paths\")\n\n./pkg/kubelet fix(kubelet): convert V().Error() to V().Info() for verbosity-aware logging #136028\n./pkg/kubelet/stats/helper.go:502:\t\tlogger.V(6).Error(err, \"Unable to fetch pod log stats\", \"pod\", klog.KRef(podNs, podName))\n./pkg/kubelet/stats/helper.go:510:\t\tlogger.V(6).Error(err, \"Unable to fetch pod etc hosts stats\", \"pod\", klog.KRef(podNs, podName))\n./pkg/kubelet/stats/cri_stats_provider.go:168:\t\tlogger.V(5).Error(err,\n./pkg/kubelet/cm/devicemanager/plugin/v1beta1/client.go:107:\t\t\tlogger.V(2).Error(err, \"Failed to close grpc connection\", \"resource\", c.Resource())\n./pkg/kubelet/cm/dra/plugin/dra_plugin_manager.go:398:\t\t\t\t\tlogger.V(3).Error(err, \"Failed to establish WatchResources stream, will retry\")\n./pkg/kubelet/kuberuntime/kuberuntime_container_linux.go:431:\t\t\tlogger.V(5).Error(fmt.Errorf(\"failed to parse /proc/self/cgroup: %w\", err), warn)\n./pkg/kubelet/kuberuntime/kuberuntime_container_linux.go:442:\t\t\tlogger.V(5).Error(err, warn)\n./pkg/kubelet/lifecycle/handlers.go:85:\t\t\tlogger.V(1).Error(err, \"Exec lifecycle hook for Container in Pod failed\", \"execCommand\", handler.Exec.Command, \"containerName\", container.Name, \"pod\", klog.KObj(pod), \"message\", string(output))\n./pkg/kubelet/lifecycle/handlers.go:93:\t\t\tlogger.V(1).Error(err, \"HTTP lifecycle hook for Container in Pod failed\", \"path\", handler.HTTPGet.Path, \"containerName\", container.Name, \"pod\", klog.KObj(pod))\n./pkg/kubelet/lifecycle/handlers.go:101:\t\t\tlogger.V(1).Error(err, \"Sleep lifecycle hook for Container in Pod failed\", \"sleepSeconds\", handler.Sleep.Seconds, \"containerName\", container.Name, \"pod\", klog.KObj(pod))\n./pkg/kubelet/lifecycle/handlers.go:152:\t\tlogger.V(1).Error(err, \"HTTPS request to lifecycle hook got HTTP response, retrying with HTTP.\", \"pod\", klog.KObj(pod), \"host\", req.URL.Host)\n./pkg/kubelet/prober/prober_manager.go:197:\t\t\t\tlogger.V(8).Error(nil, \"Startup probe already exists for container\",\n./pkg/kubelet/prober/prober_manager.go:209:\t\t\t\tlogger.V(8).Error(nil, \"Readiness probe already exists for container\",\n./pkg/kubelet/prober/prober_manager.go:221:\t\t\t\tlogger.V(8).Error(nil, \"Liveness probe already exists for container\",\n./pkg/kubelet/prober/prober.go:106:\t\tlogger.V(1).Error(err, \"Probe errored\", \"probeType\", probeType, \"pod\", klog.KObj(pod), \"podUID\", pod.UID, \"containerName\", container.Name, \"probeResult\", result)\n./pkg/kubelet/metrics/collectors/cri_metrics.go:110:\t\tlogger.V(5).Error(err, \"Descriptor not present in pre-populated list of descriptors\", \"name\", m.Name)\n./pkg/kubelet/pleg/generic.go:300:\t\t\tg.logger.V(4).Error(err, \"PLEG: Ignoring events for pod\", \"pod\", klog.KRef(pod.Namespace, pod.Name))\n./pkg/kubelet/allocation/allocation_manager.go:576:\t\tlogger.V(3).Error(err, \"Failed to delete pod allocation\", \"podUID\", uid)", "branch": "97df11dfd18", "issue_url": "https://github.com/kubernetes/kubernetes/issues/136027", "fix_url": "https://github.com/kubernetes/kubernetes/pull/136028", "issue_created": null, "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-136037", "system": "kubernetes", "issue_number": "136037", "lite": false, "title": "[Failing-test] Kubelet panic in NodeDeclareFeatures code", "description": "Which jobs are failing?\nalpha jobs\n\nWhich tests are failing?\nEntire job.\n\nSince when has it been failing?\nTest grid for some reason doesn't go very far back.\n\nTestgrid link\nhttps://testgrid.k8s.io/sig-node-containerd#ci-node-e2e-containerd-alpha-features\n\nReason for failure (if possible)\nI0105 07:36:00.527576 2667 kubelet.go:2611] \"SyncLoop DELETE\" source=\"api\" pods=[\"mirror-pod-6526/static-pod-909c75fb-fb8e-4443-b1d1-79f09ce6219a-tmp-node-e2e-9ee50a67-ubuntu-gke-2404-1-34-amd64-v20251218a\"]\npanic: runtime error: invalid memory address or nil pointer dereference\n[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1d6e0b9]\n\ngoroutine 234 [running]:\nk8s.io/kubernetes/pkg/kubelet.(*Kubelet).HandlePodUpdates(0xc000359008, {0xc00112cfa8, 0x1, 0x0?})\n\tk8s.io/kubernetes/pkg/kubelet/kubelet.go:2830 +0x459\nk8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoopIteration(0xc000359008, {0x295a2d0, 0x3b54280}, 0xc0000f5ce0, {0x2963408, 0xc000359008}, 0xc00043ee70, 0xc00043ef50, 0xc00033ff10)\n\tk8s.io/kubernetes/pkg/kubelet/kubelet.go:2613 +0xa22\nk8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoop(0xc000359008, {0x295a2d0, 0x3b54280}, 0xc0000f5ce0, {0x2963408, 0xc000359008})\n\tk8s.io/kubernetes/pkg/kubelet/kubelet.go:2542 +0x34c\nk8s.io/kubernetes/pkg/kubelet.(*Kubelet).Run(0xc000359008, 0xc0000f5ce0)\n\tk8s.io/kubernetes/pkg/kubelet/kubelet.go:1896 +0x8db\ncreated by k8s.io/kubernetes/cmd/kubelet/app.startKubelet in goroutine 1\n\tk8s.io/kubernetes/cmd/kubelet/app/server.go:1264 +0xa9\nAnything else we need to know?\nkubernetes/pkg/kubelet/kubelet.go\n\nLine 2830 in b2ac9e2\n\n oldPodInfo := &ndf.PodInfo{Spec: &oldPod.Spec, Status: &oldPod.Status} \nLooks like oldPod may not always be set so this triggers the panic.\n\nRelevant SIG(s)\n/sig node", "branch": "0f89b13c794", "issue_url": "https://github.com/kubernetes/kubernetes/issues/136031", "fix_url": "https://github.com/kubernetes/kubernetes/pull/136037", "issue_created": null, "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-136206", "system": "kubernetes", "issue_number": "136206", "lite": false, "title": "kubelet: DATA RACEs", "description": "What happened?\nSupport for race detection also in the kubelet started working in https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/133844/pull-kubernetes-e2e-kind-alpha-beta-features-race/2010727678495166464 and found (truncated list, see job for full output):\n\nDATA RACE:\n\nRead at 0x00c002b6f410 by goroutine 583:\n k8s.io/apimachinery/pkg/apis/meta/v1.(*Time).MarshalJSON()\n :1 +0x44\n encoding/json.marshalerEncoder()\n encoding/json/encode.go:483 +0x13c\n encoding/json.structEncoder.encode()\n encoding/json/encode.go:758 +0x3c7\n encoding/json.structEncoder.encode-fm()\n :1 +0xe4\n encoding/json.structEncoder.encode()\n encoding/json/encode.go:758 +0x3c7\n encoding/json.structEncoder.encode-fm()\n :1 +0xe4\n encoding/json.(*encodeState).reflectValue()\n encoding/json/encode.go:367 +0x83\n encoding/json.(*encodeState).marshal()\n encoding/json/encode.go:343 +0xdb\n encoding/json.Marshal()\n encoding/json/encode.go:209 +0x11e\n k8s.io/kubernetes/pkg/util/pod.preparePatchBytesForPodStatus()\n k8s.io/kubernetes/pkg/util/pod/pod.go:58 +0x2d3\n k8s.io/kubernetes/pkg/util/pod.PatchPodStatus()\n k8s.io/kubernetes/pkg/util/pod/pod.go:35 +0x12b\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).syncPod()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1064 +0xada\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).syncBatch()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1025 +0x199\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).Start.func1()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:260 +0x1a4\n k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:233 +0x2e\n k8s.io/apimachinery/pkg/util/wait.BackoffUntilWithContext.func1()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:255 +0x98\n k8s.io/apimachinery/pkg/util/wait.BackoffUntilWithContext()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:256 +0xed\n k8s.io/apimachinery/pkg/util/wait.BackoffUntil()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:233 +0x8a\n k8s.io/apimachinery/pkg/util/wait.JitterUntil()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:210 +0xfb\n k8s.io/apimachinery/pkg/util/wait.Until()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:163 +0x50\n k8s.io/apimachinery/pkg/util/wait.Forever()\n k8s.io/apimachinery/pkg/util/wait/wait.go:80 +0x2a\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).Start.gowrap1()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:255 +0x17\nPrevious write at 0x00c002b6f410 by goroutine 128655:\n k8s.io/kubernetes/pkg/kubelet/status.normalizeStatus.func1()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1193 +0x1ee\n k8s.io/kubernetes/pkg/kubelet/status.normalizeStatus()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1209 +0x175\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).updateStatusInternal()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:838 +0x9dc\n ...\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).SyncPod()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2100 +0x4043\n k8s.io/kubernetes/pkg/kubelet.(*podWorkers).podWorkerLoop.func1()\n k8s.io/kubernetes/pkg/kubelet/pod_workers.go:1309 +0x7ed\n k8s.io/kubernetes/pkg/kubelet.(*podWorkers).podWorkerLoop()\n k8s.io/kubernetes/pkg/kubelet/pod_workers.go:1314 +0x7ee\n k8s.io/kubernetes/pkg/kubelet.(*podWorkers).UpdatePod.func1()\n k8s.io/kubernetes/pkg/kubelet/pod_workers.go:970 +0x19c\nGoroutine 583 (running) created at:\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).Start()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:255 +0x27e\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).Run()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:1877 +0xdde\n k8s.io/kubernetes/cmd/kubelet/app.startKubelet.gowrap1()\n k8s.io/kubernetes/cmd/kubelet/app/server.go:1264 +0x50\nGoroutine 128655 (finished) created at:\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).HandlePodCleanups()\n k8s.io/kubernetes/pkg/kubelet/kubelet_pods.go:1263 +0x66f\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoopIteration()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2690 +0x29b2\n ...\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoop()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2542 +0x51d\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).Run()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:1896 +0xfea\n k8s.io/kubernetes/cmd/kubelet/app.startKubelet.gowrap1()\n k8s.io/kubernetes/cmd/kubelet/app/server.go:1264 +0x50\nDATA RACE:\n\nWrite at 0x00c0009c0178 by goroutine 129432:\n k8s.io/kubernetes/pkg/kubelet/status.normalizeStatus.func1()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1193 +0x1ee\n k8s.io/kubernetes/pkg/kubelet/status.normalizeStatus()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1209 +0x175\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).updateStatusInternal()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:838 +0x9dc\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).TerminatePod()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:637 +0x1228\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).SyncTerminatedPod()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2409 +0x17f5\n ...\n k8s.io/kubernetes/pkg/kubelet/kuberuntime.(*kubeGenericRuntimeManager).SyncPod()\n k8s.io/kubernetes/pkg/kubelet/kuberuntime/kuberuntime_manager.go:1543 +0x2114\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).SyncPod()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2162 +0x2e41\n k8s.io/kubernetes/pkg/kubelet/cm.(*podContainerManagerImpl).EnsureExists()\n k8s.io/kubernetes/pkg/kubelet/cm/pod_container_manager_linux.go:100 +0x7c1\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).SyncPod()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2104 +0x4387\n k8s.io/kubernetes/pkg/kubelet/cm.(*qosContainerManagerImpl).UpdateCgroups()\n k8s.io/kubernetes/pkg/kubelet/cm/qos_container_manager_linux.go:361 +0xe30\n k8s.io/kubernetes/pkg/kubelet/cm.(*containerManagerImpl).UpdateQOSCgroups()\n k8s.io/kubernetes/pkg/kubelet/cm/container_manager_linux.go:606 +0x76\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).SyncPod()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2100 +0x4043\n k8s.io/kubernetes/pkg/kubelet.(*podWorkers).podWorkerLoop.func1()\n k8s.io/kubernetes/pkg/kubelet/pod_workers.go:1309 +0x7ed\n k8s.io/kubernetes/pkg/kubelet.(*podWorkers).podWorkerLoop()\n k8s.io/kubernetes/pkg/kubelet/pod_workers.go:1314 +0x7ee\n k8s.io/kubernetes/pkg/kubelet.(*podWorkers).UpdatePod.func1()\n k8s.io/kubernetes/pkg/kubelet/pod_workers.go:970 +0x19c\nPrevious read at 0x00c0009c0178 by goroutine 583:\n k8s.io/apimachinery/pkg/apis/meta/v1.(*Time).MarshalJSON()\n :1 +0x44\n encoding/json.marshalerEncoder()\n encoding/json/encode.go:483 +0x13c\n encoding/json.structEncoder.encode()\n encoding/json/encode.go:758 +0x3c7\n encoding/json.structEncoder.encode-fm()\n :1 +0xe4\n encoding/json.structEncoder.encode()\n encoding/json/encode.go:758 +0x3c7\n encoding/json.structEncoder.encode-fm()\n :1 +0xe4\n encoding/json.(*encodeState).reflectValue()\n encoding/json/encode.go:367 +0x83\n encoding/json.(*encodeState).marshal()\n encoding/json/encode.go:343 +0xdb\n encoding/json.Marshal()\n encoding/json/encode.go:209 +0x11e\n k8s.io/kubernetes/pkg/util/pod.preparePatchBytesForPodStatus()\n k8s.io/kubernetes/pkg/util/pod/pod.go:58 +0x2d3\n k8s.io/kubernetes/pkg/util/pod.PatchPodStatus()\n k8s.io/kubernetes/pkg/util/pod/pod.go:35 +0x12b\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).syncPod()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1064 +0xada\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).syncBatch()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1025 +0x199\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).Start.func1()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:260 +0x1a4\n k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:233 +0x2e\n k8s.io/apimachinery/pkg/util/wait.BackoffUntilWithContext.func1()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:255 +0x98\n k8s.io/apimachinery/pkg/util/wait.BackoffUntilWithContext()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:256 +0xed\n k8s.io/apimachinery/pkg/util/wait.BackoffUntil()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:233 +0x8a\n k8s.io/apimachinery/pkg/util/wait.JitterUntil()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:210 +0xfb\n k8s.io/apimachinery/pkg/util/wait.Until()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:163 +0x50\n k8s.io/apimachinery/pkg/util/wait.Forever()\n k8s.io/apimachinery/pkg/util/wait/wait.go:80 +0x2a\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).Start.gowrap1()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:255 +0x17\nGoroutine 129432 (running) created at:\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).HandlePodCleanups()\n k8s.io/kubernetes/pkg/kubelet/kubelet_pods.go:1263 +0x66f\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoopIteration()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2690 +0x29b2\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoop()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2542 +0x51d\n k8s.io/kubernetes/pkg/kubelet/container.(*runtimeCache).ForceUpdateIfOlder()\n k8s.io/kubernetes/pkg/kubelet/container/runtime_cache.go:77 +0x130\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).HandlePodCleanups()\n k8s.io/kubernetes/pkg/kubelet/kubelet_pods.go:1263 +0x66f\n ...\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoop()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2542 +0x51d\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).Run()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:1896 +0xfea\n k8s.io/kubernetes/cmd/kubelet/app.startKubelet.gowrap1()\n k8s.io/kubernetes/cmd/kubelet/app/server.go:1264 +0x50\nGoroutine 583 (running) created at:\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).Start()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:255 +0x27e\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).Run()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:1877 +0xdde\n k8s.io/kubernetes/cmd/kubelet/app.startKubelet.gowrap1()\n k8s.io/kubernetes/cmd/kubelet/app/server.go:1264 +0x50\nDATA RACE:\n\nRead at 0x00c001ba0180 by goroutine 583:\n k8s.io/apimachinery/pkg/apis/meta/v1.(*Time).MarshalJSON()\n :1 +0x44\n encoding/json.marshalerEncoder()\n encoding/json/encode.go:483 +0x13c\n encoding/json.structEncoder.encode()\n encoding/json/encode.go:758 +0x3c7\n encoding/json.structEncoder.encode-fm()\n :1 +0xe4\n encoding/json.structEncoder.encode()\n encoding/json/encode.go:758 +0x3c7\n encoding/json.structEncoder.encode-fm()\n :1 +0xe4\n encoding/json.(*encodeState).reflectValue()\n encoding/json/encode.go:367 +0x83\n encoding/json.(*encodeState).marshal()\n encoding/json/encode.go:343 +0xdb\n encoding/json.Marshal()\n encoding/json/encode.go:209 +0x11e\n k8s.io/kubernetes/pkg/util/pod.preparePatchBytesForPodStatus()\n k8s.io/kubernetes/pkg/util/pod/pod.go:58 +0x2d3\n k8s.io/kubernetes/pkg/util/pod.PatchPodStatus()\n k8s.io/kubernetes/pkg/util/pod/pod.go:35 +0x12b\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).syncPod()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1064 +0xada\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).syncBatch()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1025 +0x199\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).Start.func1()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:260 +0x1a4\n k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:233 +0x2e\n k8s.io/apimachinery/pkg/util/wait.BackoffUntilWithContext.func1()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:255 +0x98\n k8s.io/apimachinery/pkg/util/wait.BackoffUntilWithContext()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:256 +0xed\n k8s.io/apimachinery/pkg/util/wait.BackoffUntil()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:233 +0x8a\n k8s.io/apimachinery/pkg/util/wait.JitterUntil()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:210 +0xfb\n k8s.io/apimachinery/pkg/util/wait.Until()\n k8s.io/apimachinery/pkg/util/wait/backoff.go:163 +0x50\n k8s.io/apimachinery/pkg/util/wait.Forever()\n k8s.io/apimachinery/pkg/util/wait/wait.go:80 +0x2a\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).Start.gowrap1()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:255 +0x17\nPrevious write at 0x00c001ba0180 by goroutine 165064:\n k8s.io/kubernetes/pkg/kubelet/status.normalizeStatus.func1()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1193 +0x1ee\n k8s.io/kubernetes/pkg/kubelet/status.normalizeStatus()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:1209 +0x175\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).updateStatusInternal()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:838 +0x9dc\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).TerminatePod()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:637 +0x1228\n ...\n k8s.io/kubernetes/pkg/kubelet.(*podWorkers).podWorkerLoop.func1()\n k8s.io/kubernetes/pkg/kubelet/pod_workers.go:1309 +0x7ed\n k8s.io/kubernetes/pkg/kubelet.(*podWorkers).podWorkerLoop()\n k8s.io/kubernetes/pkg/kubelet/pod_workers.go:1314 +0x7ee\n k8s.io/kubernetes/pkg/kubelet.(*podWorkers).UpdatePod.func1()\n k8s.io/kubernetes/pkg/kubelet/pod_workers.go:970 +0x19c\nGoroutine 583 (running) created at:\n k8s.io/kubernetes/pkg/kubelet/status.(*manager).Start()\n k8s.io/kubernetes/pkg/kubelet/status/status_manager.go:255 +0x27e\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).Run()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:1877 +0xdde\n k8s.io/kubernetes/cmd/kubelet/app.startKubelet.gowrap1()\n k8s.io/kubernetes/cmd/kubelet/app/server.go:1264 +0x50\nGoroutine 165064 (running) created at:\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).HandlePodCleanups()\n k8s.io/kubernetes/pkg/kubelet/kubelet_pods.go:1263 +0x66f\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoopIteration()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2690 +0x29b2\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).syncLoop()\n k8s.io/kubernetes/pkg/kubelet/kubelet.go:2542 +0x51d\n k8s.io/kubernetes/pkg/kubelet/container.(*runtimeCache).ForceUpdateIfOlder()\n k8s.io/kubernetes/pkg/kubelet/container/runtime_cache.go:77 +0x130\n k8s.io/kubernetes/pkg/kubelet.(*Kubelet).HandlePodCleanups()\n k8s.io/kubernetes/pkg/kubelet/kubelet_pods.go:1263 +0x66f", "branch": "664efa86275", "issue_url": "https://github.com/kubernetes/kubernetes/issues/136179", "fix_url": "https://github.com/kubernetes/kubernetes/pull/136206", "issue_created": null, "severity": "Blocker", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-136450", "system": "kubernetes", "issue_number": "136450", "lite": false, "title": "DRA: support non-pod references in ReservedFor", "description": "TheResourceClaim controller would fail to process and clean up stale pod references if it encountered any non-pod references in the status.reservedFor field. This halted the controller's operation, preventing necessary cleanup.", "branch": "bcdc613966e613aa3d7f5106c013c8650a0edecf", "issue_url": "https://github.com/kubernetes/kubernetes/pull/136450", "fix_url": "https://github.com/kubernetes/kubernetes/pull/136450", "issue_created": null, "severity": "Critical", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-136509", "system": "kubernetes", "issue_number": "136509", "lite": false, "title": "client-go informers: fix potential deadlock", "description": "In the unlikely situation that sharedProcessor.distribute was triggered by a resync before sharedProcessor.run had a chance to start the listeners, the sharedProcessor deadlocked: sharedProcessor.distribute held a read/write lock on listenersLock while being blocked on the write to the listener's channel. The listeners who would have read from those weren't get started because sharedProcessor.run was blocked trying to get a read lock for listenersLock.\n\nThis gets fixed by releasing the read/write lock in sharedProcessor.distribute while waiting for all listeners to be started. Because either all or no listeners are started, the existing global listenersStarted boolean is sufficient.\n\nThe TestListenerResyncPeriods tests now runs twice, with and without the artificial delay. It gets converted to a synctest, so it executes quickly despite the time.Sleep calls and timing is deterministic. The enhanced log output confirms that with the delay, the initial sync completes later:\n\n=== RUN TestListenerResyncPeriods\n shared_informer_test.go:236: 0s: listener3: handle: pod1\n shared_informer_test.go:236: 0s: listener3: handle: pod2\n shared_informer_test.go:236: 0s: listener1: handle: pod1\n shared_informer_test.go:236: 0s: listener1: handle: pod2\n shared_informer_test.go:236: 0s: listener2: handle: pod1\n shared_informer_test.go:236: 0s: listener2: handle: pod2\n shared_informer_test.go:236: 2s: listener2: handle: pod1\n shared_informer_test.go:236: 2s: listener2: handle: pod2\n shared_informer_test.go:236: 3s: listener3: handle: pod1\n shared_informer_test.go:236: 3s: listener3: handle: pod2\n--- PASS: TestListenerResyncPeriods (0.00s)\n=== RUN TestListenerResyncPeriodsDelayed\n shared_informer_test.go:236: 1s: listener1: handle: pod1\n shared_informer_test.go:236: 1s: listener1: handle: pod2\n shared_informer_test.go:236: 1s: listener2: handle: pod1\n shared_informer_test.go:236: 1s: listener2: handle: pod2\n shared_informer_test.go:236: 1s: listener3: handle: pod1\n shared_informer_test.go:236: 1s: listener3: handle: pod2\n shared_informer_test.go:236: 2s: listener2: handle: pod1\n shared_informer_test.go:236: 2s: listener2: handle: pod2\n shared_informer_test.go:236: 3s: listener3: handle: pod1\n shared_informer_test.go:236: 3s: listener3: handle: pod2\n--- PASS: TestListenerResyncPeriodsDelayed (0.00s)", "branch": "8f4c197169b", "issue_url": "https://github.com/kubernetes/kubernetes/pull/136509", "fix_url": "https://github.com/kubernetes/kubernetes/pull/136509", "issue_created": null, "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "kubernetes-136534", "system": "kubernetes", "issue_number": "136534", "lite": false, "title": "panic: assignment to entry in nil map in pkg/util/resource.maxResourceList when pod container has nil Resources.Requests", "description": "What happened?\nWhen using PodRequestsAndLimits() to calculate pod resource requests, a panic occurs when comparing spec container resources with status container resources, and the spec has nil Resources.Requests while the status has populated values.\n\npanic: assignment to entry in nil map\n\ngoroutine 586 [running]:\nk8s.io/kubectl/pkg/util/resource.maxResourceList(0x0, 0x0?)\n /go/pkg/mod/k8s.io/kubectl@v0.34.0/pkg/util/resource/resource.go:179 +0x190\nk8s.io/kubectl/pkg/util/resource.max(0x18?, {0x4003797b68, 0x2, 0x0?})\n /go/pkg/mod/k8s.io/kubectl@v0.34.0/pkg/util/resource/resource.go:157 +0x60\nk8s.io/kubectl/pkg/util/resource.determineContainerReqs(...)\n /go/pkg/mod/k8s.io/kubectl@v0.34.0/pkg/util/resource/resource.go:149 +0x148\nk8s.io/kubectl/pkg/util/resource.podRequests(...)\n /go/pkg/mod/k8s.io/kubectl@v0.34.0/pkg/util/resource/resource.go:57 +0x254\nk8s.io/kubectl/pkg/util/resource.PodRequestsAndLimits(...)\n /go/pkg/mod/k8s.io/kubectl@v0.34.0/pkg/util/resource/resource.go:36 +0x20\nWhat did you expect to happen?\nThe function should handle nil ResourceList gracefully and return an empty or properly initialized ResourceList instead of panicking.\n\nHow can we reproduce it?\nThe determineContainerReqs function compares spec and status resources:\n\nreqs := max(container.Resources.Requests, // from pod.spec.containers[].resources.requests\n containerStatus.AllocatedResources, // from pod.status.containerStatuses[].allocatedResources\n containerStatus.Resources.Requests) // from pod.status.containerStatuses[].resources.requests\nThe panic occurs when:\n\nspec.containers[].resources.requests is nil (pod doesn't define resource requests)\nstatus.containerStatuses[].resources.requests has values (populated by kubelet or admission controllers)\nAny code calls PodRequestsAndLimits() on that pod\nThis state can occur when:\n\nA LimitRange with defaultRequest applies defaults to pods without explicit requests\nThe kubelet populates status.containerStatuses[].resources with actual values\nVirtual cluster (vcluster) syncers copy status back but don't modify spec\nExample pod state that triggers the panic:\n\n{\n \"spec\": {\n \"containers\": [{\n \"resources\": {}\n }]\n },\n \"status\": {\n \"containerStatuses\": [{\n \"resources\": {\n \"requests\": {\"cpu\": \"100m\", \"memory\": \"128Mi\"}\n }\n }]\n }\n}", "branch": "4ffc49fb3e4", "issue_url": "https://github.com/kubernetes/kubernetes/issues/136533", "fix_url": "https://github.com/kubernetes/kubernetes/pull/136534", "issue_created": null, "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Hard", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ray-8749", "system": "ray", "issue_number": "8749", "lite": true, "title": "rerunning script causes error with 'Address already in use'", "description": "What is the problem?\nray latest master\npython 3.7.6\nOS: redhat 7.7\n\nI have a script that if I run it it works fine, the second time it runs fine to completion (no changes in parameters), but either on the 3rd or fourth time I get the following segfault:\n\n$/opt/conda/bin/python test_program.py\n\nWARNING: Logging before InitGoogleLogging() is written to STDERR\n\nI0602 18:09:25.494333 1188864 1188864 global_state_accessor.cc:25] Redis server address = 192.1681.1.183:6379, is test flag = 0\n\nI0602 18:09:25.495889 1188864 1188864 redis_client.cc:141] RedisClient connected.\n\nI0602 18:09:25.503971 1188864 1188864 redis_gcs_client.cc:88] RedisGcsClient Connected.\n\nI0602 18:09:25.504889 1188864 1188864 service_based_gcs_client.cc:75] ServiceBasedGcsClient Connected.\n\nE0602 18:09:25.512972839 1188864 server_chttp2.cc:40] {\"created\":\"@1591121365.512899346\",\"description\":\"No address added out of total 1 resolved\",\"file\":\"external/com_github_grpc_grpc/src/core/ext/transport/chttp2/server/chttp2_server.cc\",\"file_line\":394,\"referenced_errors\":[{\"created\":\"@1591121365.512896692\",\"description\":\"Failed to add any wildcard listeners\",\"file\":\"external/com_github_grpc_grpc/src/core/lib/iomgr/tcp_server_posix.cc\",\"file_line\":341,\"referenced_errors\":[{\"created\":\"@1591121365.512886167\",\"description\":\"Unable to configure socket\",\"fd\":15,\"file\":\"external/com_github_grpc_grpc/src/core/lib/iomgr/tcp_server_utils_posix_common.cc\",\"file_line\":208,\"referenced_errors\":[{\"created\":\"@1591121365.512882261\",\"description\":\"Address already in use\",\"errno\":98,\"file\":\"external/com_github_grpc_grpc/src/core/lib/iomgr/tcp_server_utils_posix_common.cc\",\"file_line\":181,\"os_error\":\"Address already in use\",\"syscall\":\"bind\"}]},{\"created\":\"@1591121365.512896152\",\"description\":\"Unable to configure socket\",\"fd\":15,\"file\":\"external/com_github_grpc_grpc/src/core/lib/iomgr/tcp_server_utils_posix_common.cc\",\"file_line\":208,\"referenced_errors\":[{\"created\":\"@1591121365.512894081\",\"description\":\"Address already in use\",\"errno\":98,\"file\":\"external/com_github_grpc_grpc/src/core/lib/iomgr/tcp_server_utils_posix_common.cc\",\"file_line\":181,\"os_error\":\"Address already in use\",\"syscall\":\"bind\"}]}]}]}\n\n*** Aborted at 1591121365 (unix time) try \"date -d @1591121365\" if you are using GNU date ***\n\nPC: @ 0x0 (unknown)\n\n*** SIGSEGV (@0x0) received by PID 1188864 (TID 0x7f27706b6740) from PID 0; stack trace: ***\n\n@ 0x7f2770297630 (unknown)\n\n@ 0x7f2768732002 grpc::ServerInterface::RegisteredAsyncRequest::IssueRequest()\n\n@ 0x7f27683e0c09 ray::rpc::CoreWorkerService::WithAsyncMethod_AssignTask<>::RequestAssignTask()\n\n@ 0x7f276841a1ab ray::rpc::ServerCallFactoryImpl<>::CreateCall()\n\n@ 0x7f276868ddc1 ray::rpc::GrpcServer::Run()\n\n@ 0x7f276842ea92 ray::CoreWorker::CoreWorker()\n\n@ 0x7f27684327f4 ray::CoreWorkerProcess::CreateWorker()\n\n@ 0x7f2768432d7f ray::CoreWorkerProcess::CoreWorkerProcess()\n\n@ 0x7f27684333cb ray::CoreWorkerProcess::Initialize()\n\n@ 0x7f276839d3c4 __pyx_pw_3ray_7_raylet_10CoreWorker_1__cinit__()\n\n@ 0x7f276839e4a5 __pyx_tp_new_3ray_7_raylet_CoreWorker()\n\n@ 0x563da5958dc9 _PyObject_FastCallKeywords\n\n@ 0x563da59a8e8f _PyEval_EvalFrameDefault\n\n@ 0x563da58fe030 _PyEval_EvalCodeWithName\n\n@ 0x563da5943917 _PyFunction_FastCallKeywords\n\n@ 0x563da59a50a6 _PyEval_EvalFrameDefault\n\n@ 0x563da58fd6f9 _PyEval_EvalCodeWithName\n\n@ 0x563da5943917 _PyFunction_FastCallKeywords\n\n@ 0x563da59a50a6 _PyEval_EvalFrameDefault\n\n@ 0x563da58fd6f9 _PyEval_EvalCodeWithName\n\n@ 0x563da58fe5f4 PyEval_EvalCodeEx\n\n@ 0x563da58fe61c PyEval_EvalCode\n\n@ 0x563da59ff974 run_mod\n\n@ 0x563da5a09cf1 PyRun_FileExFlags\n\n@ 0x563da5a09ee3 PyRun_SimpleFileExFlags\n\n@ 0x563da5a0af95 pymain_main\n\n@ 0x563da5a0b0bc _Py_UnixMain\n\n@ 0x7f276fedc545 __libc_start_main\n\n@ 0x563da59b3990 (unknown)\nSegmentation fault\n\nAt this point ray is in a bad state and I need to restart the cluster. Any help would be appreciated.\n\nthanks,\nLuke", "branch": "890cb8cb70f095c146e747db2c3368f6af1931fa", "issue_url": "https://github.com/ray-project/ray/issues/8749", "fix_url": "https://github.com/ray-project/ray/pull/8773", "issue_created": "2020-06-02", "severity": "Critical", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ray-8889", "system": "ray", "issue_number": "8889", "lite": false, "title": "[RLlib] PPO not learning in complex cont. action environments.", "description": "PPO is currently not learning e.g. HalfCheetah-v2 using the tuned_examples/ppo/halfcheetah-ppo.yaml config (on neither tf nor torch).\n\nray-0.9.0dev\ntf2.2.0\ntorch1.5.0\n\nThe problem does not occur on ray/rllib 0.8.5.", "branch": "a90cd0fcbb81c2be472b16c61bebc75125d16133", "issue_url": "https://github.com/ray-project/ray/issues/8889", "fix_url": "https://github.com/ray-project/ray/pull/8898", "issue_created": "2020-06-22", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 1} {"instance_id": "ray-14264", "system": "ray", "issue_number": "14264", "lite": true, "title": "[autoscaler] wrongly shuts down all nodes due to one bad node", "description": "the autoscaler tries take down one idle (false positive though, the node was running at 100% cpu) node but end up killing every nodes due to an internal key error. It seems to get confused with the mapping. this is a serious issue as all my progress get lost. I was using 16 placement group (on one machine each).\n\n2021-02-17 14:55:34,817 INFO monitor.py:207 – :event_summary:Removing 1 nodes of type cpu_48_spot (idle).\n2021-02-17 14:55:34,817 INFO monitor.py:207 – :event_summary:Adding 1 nodes of type cpu_48_spot.\n2021-02-17 14:55:40,430 INFO load_metrics.py:102 – LoadMetrics: Removed mapping: 172.31.23.116 - 1613573430.7000167\n2021-02-17 14:55:40,430 INFO load_metrics.py:109 – LoadMetrics: Removed 1 stale ip mappings: {‘172.31.23.116’} not in {‘172.31.16.240’, ‘172.31.27.173’, ‘172.31.26.163’, ‘172.31.20.177’, ‘172.31.25.79’, ‘172.31.28.159’, ‘172.31.21.227’, ‘172.31.24.131’, ‘172.31.31.164’, ‘172.31.22.24’, ‘172.31.26.41’, ‘172.31.19.126’, ‘172.31.22.66’, ‘172.31.26.13’, ‘172.31.30.105’, ‘172.31.25.157’, ‘172.31.27.26’}\n2021-02-17 14:55:40,744 ERROR autoscaler.py:266 – StandardAutoscaler: i-02b77234ffad2072c: Terminating failed to setup/initialize node.\n2021-02-17 14:55:40,744 ERROR autoscaler.py:139 – StandardAutoscaler: Error during autoscaling.\nTraceback (most recent call last):\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 137, in update\nself._update()\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 270, in _update\nself._get_node_type(node_id) + \" (launch failed).\",\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 598, in _get_node_type\nnode_tags = self.provider.node_tags(node_id)\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/aws/node_provider.py”, line 170, in node_tags\nd1 = self.tag_cache[node_id]\nKeyError: ‘i-02b77234ffad2072c’\n2021-02-17 14:55:46,909 ERROR autoscaler.py:266 – StandardAutoscaler: i-02b77234ffad2072c: Terminating failed to setup/initialize node.\n2021-02-17 14:55:46,909 ERROR autoscaler.py:139 – StandardAutoscaler: Error during autoscaling.\nTraceback (most recent call last):\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 137, in update\nself._update()\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 270, in _update\nself._get_node_type(node_id) + \" (launch failed).\",\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 598, in _get_node_type\nnode_tags = self.provider.node_tags(node_id)\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/aws/node_provider.py”, line 170, in node_tags\nd1 = self.tag_cache[node_id]\nKeyError: ‘i-02b77234ffad2072c’\n2021-02-17 14:55:47,082 INFO monitor.py:207 – :event_summary:Resized to 724 CPUs.\n2021-02-17 14:55:52,997 ERROR autoscaler.py:266 – StandardAutoscaler: i-02b77234ffad2072c: Terminating failed to setup/initialize node.\n2021-02-17 14:55:52,998 ERROR autoscaler.py:139 – StandardAutoscaler: Error during autoscaling.\nTraceback (most recent call last):\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 137, in update\nself._update()\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 270, in _update\nself._get_node_type(node_id) + \" (launch failed).\",\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 598, in _get_node_type\nnode_tags = self.provider.node_tags(node_id)\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/aws/node_provider.py”, line 170, in node_tags\nd1 = self.tag_cache[node_id]\nKeyError: ‘i-02b77234ffad2072c’\n2021-02-17 14:55:58,965 ERROR autoscaler.py:266 – StandardAutoscaler: i-02b77234ffad2072c: Terminating failed to setup/initialize node.\n2021-02-17 14:55:58,965 ERROR autoscaler.py:139 – StandardAutoscaler: Error during autoscaling.\nTraceback (most recent call last):\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 137, in update\nself._update()\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 270, in _update\nself._get_node_type(node_id) + \" (launch failed).\",\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 598, in _get_node_type\nnode_tags = self.provider.node_tags(node_id)\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/aws/node_provider.py”, line 170, in node_tags\nd1 = self.tag_cache[node_id]\nKeyError: ‘i-02b77234ffad2072c’\n2021-02-17 14:56:05,002 ERROR autoscaler.py:266 – StandardAutoscaler: i-02b77234ffad2072c: Terminating failed to setup/initialize node.\n2021-02-17 14:56:05,003 ERROR autoscaler.py:139 – StandardAutoscaler: Error during autoscaling.\nTraceback (most recent call last):\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 137, in update\nself._update()\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 270, in _update\nself._get_node_type(node_id) + \" (launch failed).\",\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 598, in _get_node_type\nnode_tags = self.provider.node_tags(node_id)\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/aws/node_provider.py”, line 170, in node_tags\nd1 = self.tag_cache[node_id]\nKeyError: ‘i-02b77234ffad2072c’\n2021-02-17 14:56:10,999 ERROR autoscaler.py:266 – StandardAutoscaler: i-02b77234ffad2072c: Terminating failed to setup/initialize node.\n2021-02-17 14:56:11,000 ERROR autoscaler.py:139 – StandardAutoscaler: Error during autoscaling.\nTraceback (most recent call last):\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 137, in update\nself._update()\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 270, in _update\nself._get_node_type(node_id) + \" (launch failed).\",\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 598, in _get_node_type\nnode_tags = self.provider.node_tags(node_id)\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/aws/node_provider.py”, line 170, in node_tags\nd1 = self.tag_cache[node_id]\nKeyError: ‘i-02b77234ffad2072c’\n2021-02-17 14:56:11,001 CRITICAL autoscaler.py:152 – StandardAutoscaler: Too many errors, abort.\n2021-02-17 14:56:11,001 ERROR monitor.py:271 – Error in monitor loop\nTraceback (most recent call last):\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/monitor.py”, line 269, in run\nself._run()\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/monitor.py”, line 202, in _run\nself.autoscaler.update()\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 154, in update\nraise e\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 137, in update\nself._update()\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 270, in _update\nself._get_node_type(node_id) + \" (launch failed).\",\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/autoscaler.py”, line 598, in _get_node_type\nnode_tags = self.provider.node_tags(node_id)\nFile “/home/centos/.local/lib/python3.7/site-packages/ray/autoscaler/_private/aws/node_provider.py”, line 170, in node_tags\nd1 = self.tag_cache[node_id]\nKeyError: ‘i-02b77234ffad2072c’\n2021-02-17 14:56:11,002 ERROR autoscaler.py:724 – StandardAutoscaler: kill_workers triggered\n2021-02-17 14:56:11,453 ERROR autoscaler.py:729 – StandardAutoscaler: terminated 16 node(s)\n2021-02-17 14:56:11,453 INFO monitor.py:250 – Monitor: Exception caught. Taking down workers…\n2021-02-17 14:56:11,680 INFO monitor.py:262 – Monitor: Workers taken down.", "branch": "d921dca075456203727bff09329923e6b210cc3d", "issue_url": "https://github.com/ray-project/ray/issues/14264", "fix_url": "https://github.com/ray-project/ray/pull/14424", "issue_created": "2021-02-23", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ray-14883", "system": "ray", "issue_number": "14883", "lite": false, "title": "[core] Node's reported static resources corrupted after creating a placement group", "description": "It seems that the reported \"total\" (static) resources for nodes are sometimes corrupted when using placement groups. The issue is easy to reproduce, if I run the following script:\n\nimport ray\nray.init()\n\npg = ray.util.placement_group([{\"CPU\": 1}])\nimport time\ntime.sleep(999)\nSometimes I get (correct):\n\nUsage:\n 1.0/8.0 CPU\n 0.0/1.0 CPU_group_0_96ba2e7864f6042c4b829cb2ba0f15ff\n 0.0/1.0 CPU_group_96ba2e7864f6042c4b829cb2ba0f15ff\n 0.00/8.035 GiB memory\n 0.00/4.017 GiB object_store_memory\nand sometimes this (incorrect--- and even the other resources have gone missing!)\n\nUsage:\n 0.0/1.0 CPU_group_0_a38a03683b26d7b35c3f1fbf53fefc92\n 0.0/1.0 CPU_group_a38a03683b26d7b35c3f1fbf53fefc92\nOriginal issue:\nI started a cluster, I run the following commands:\n\nimport ray\nfrom ray.util import placement_group\npg = placement_group([{\"CPU\": 1, \"GPU\": 1}] + [{\"CPU\": 1}] * 100, name=\"__test_\")\nray.get(pg.ready())\n#wait..\nthe event summarized prints:\n\n(autoscaler +7m58s) Resized to 10 CPUs, 1 GPUs.\n(autoscaler +8m5s) Resized to 16 CPUs, 1 GPUs.\n(autoscaler +8m12s) Resized to 36 CPUs, 1 GPUs.\n(autoscaler +8m19s) Resized to 68 CPUs, 1 GPUs.\n(autoscaler +8m26s) Resized to 86 CPUs, 1 GPUs.\n\n>>> (autoscaler +8m33s) Resized to 100 CPUs, 1 GPUs.\n (autoscaler +8m40s) Resized to 80 CPUs, 1 GPUs.\n\n>>> (autoscaler +8m47s) Resized to 52 CPUs.\n(autoscaler +8m53s) Resized to 64 CPUs.\n(autoscaler +9m0s) Resized to 56 CPUs.\n(autoscaler +9m6s) Resized to 96 CPUs, 1 GPUs.\n(autoscaler +9m13s) Resized to 76 CPUs.\n(autoscaler +9m19s) Resized to 54 CPUs.\nlooking at the logs (49 ray.worker.default are always Healthy, but the utilization keeps changing from 10/10-100/100 back and forth:\n\nNode status\n---------------------------------------------------------------\nHealthy:\n 1 ray.head.default\n 49 ray.worker.default\nPending:\n (no pending nodes)\nRecent failures:\n (no failures)\n\nResources\n---------------------------------------------------------------\n\nUsage:\n 77.0/78.0 CPU\n 0.0/71.0 CPU_group_0412ba1eeb915fbd679e1a13b51bcaa3\ncluster yaml:\n\n# An unique identifier for the head node and workers of this cluster.\ncluster_name: ameer_rllib_default\n\n# The maximum number of workers nodes to launch in addition to the head\n# node.\nmax_workers: 100\n\n# The autoscaler will scale up the cluster faster with higher upscaling speed.\n# E.g., if the task requires adding more nodes then autoscaler will gradually\n# scale up the cluster in chunks of upscaling_speed*currently_running_nodes.\n# This number should be > 0.\nupscaling_speed: 100.0\n\n# This executes all commands on all nodes in the docker container,\n# and opens all the necessary ports to support the Ray cluster.\n# Empty string means disabled.\ndocker:\n image: \"rayproject/ray-ml:nightly-gpu\" # You can change this to latest-cpu if you don't need GPU support and want a faster startup\n # image: rayproject/ray:latest-gpu # use this one if you don't need ML dependencies, it's faster to pull\n container_name: \"ray_container\"\n # If true, pulls latest version of image. Otherwise, `docker run` will only pull the image\n # if no cached version is present.\n pull_before_run: True\n run_options: [] # Extra options to pass into \"docker run\"\n\n # Example of running a GPU head with CPU workers\n # head_image: \"rayproject/ray-ml:latest-gpu\"\n # Allow Ray to automatically detect GPUs\n\n # worker_image: \"rayproject/ray-ml:latest-cpu\"\n # worker_run_options: []\n\n# If a node is idle for this many minutes, it will be removed.\nidle_timeout_minutes: 5\n\n# Cloud-provider specific configuration.\nprovider:\n type: aws\n region: us-west-2\n # Availability zone(s), comma-separated, that nodes may be launched in.\n # Nodes are currently spread between zones by a round-robin approach,\n # however this implementation detail should not be relied upon.\n availability_zone: us-west-2a,us-west-2b\n # Whether to allow node reuse. If set to False, nodes will be terminated\n # instead of stopped.\n cache_stopped_nodes: True # If not present, the default is True.\n\n# How Ray will authenticate with newly launched nodes.\nauth:\n ssh_user: ubuntu\n# By default Ray creates a new private keypair, but you can also use your own.\n# If you do so, make sure to also set \"KeyName\" in the head and worker node\n# configurations below.\n# ssh_private_key: /path/to/your/key.pem\n\n# Tell the autoscaler the allowed node types and the resources they provide.\n# The key is the name of the node type, which is just for debugging purposes.\n# The node config specifies the launch config and physical instance type.\navailable_node_types:\n ray.head.default:\n # The minimum number of worker nodes of this type to launch.\n # This number should be >= 0.\n min_workers: 0\n # The maximum number of worker nodes of this type to launch.\n # This takes precedence over min_workers.\n max_workers: 0\n # The node type's CPU and GPU resources are auto-detected based on AWS instance type.\n # If desired, you can override the autodetected CPU and GPU resources advertised to the autoscaler.\n # You can also set custom resources.\n # For example, to mark a node type as having 1 CPU, 1 GPU, and 5 units of a resource called \"custom\", set\n # resources: {\"CPU\": 1, \"GPU\": 1, \"custom\": 5}\n resources: {}\n # Provider-specific config for this node type, e.g. instance type. By default\n # Ray will auto-configure unspecified fields such as SubnetId and KeyName.\n # For more documentation on available fields, see:\n # http://boto3.readthedocs.io/en/latest/reference/services/ec2.html#EC2.ServiceResource.create_instances\n node_config:\n InstanceType: p2.xlarge\n ImageId: ami-0a2363a9cff180a64 # Deep Learning AMI (Ubuntu) Version 30\n # You can provision additional disk space with a conf as follows\n BlockDeviceMappings:\n - DeviceName: /dev/sda1\n Ebs:\n VolumeSize: 100\n # Additional options in the boto docs.\n ray.worker.default:\n # The minimum number of worker nodes of this type to launch.\n # This number should be >= 0.\n min_workers: 0\n # The maximum number of worker nodes of this type to launch.\n # This takes precedence over min_workers.\n max_workers: 100\n # The node type's CPU and GPU resources are auto-detected based on AWS instance type.\n # If desired, you can override the autodetected CPU and GPU resources advertised to the autoscaler.\n # You can also set custom resources.\n # For example, to mark a node type as having 1 CPU, 1 GPU, and 5 units of a resource called \"custom\", set\n # resources: {\"CPU\": 1, \"GPU\": 1, \"custom\": 5}\n resources: {}\n # Provider-specific config for this node type, e.g. instance type. By default\n # Ray will auto-configure unspecified fields such as SubnetId and KeyName.\n # For more documentation on available fields, see:\n # http://boto3.readthedocs.io/en/latest/reference/services/ec2.html#EC2.ServiceResource.create_instances\n node_config:\n InstanceType: m5.large\n ImageId: ami-0a2363a9cff180a64 # Deep Learning AMI (Ubuntu) Version 30\n # Run workers on spot by default. Comment this out to use on-demand.\n InstanceMarketOptions:\n MarketType: spot\n # Additional options can be found in the boto docs, e.g.\n # SpotOptions:\n # MaxPrice: MAX_HOURLY_PRICE\n # Additional options in the boto docs.\n\n# Specify the node type of the head node (as configured above).\nhead_node_type: ray.head.default\n\n# Files or directories to copy to the head and worker nodes. The format is a\n# dictionary from REMOTE_PATH: LOCAL_PATH, e.g.\nfile_mounts:\n \"~/tennis\": \"./tennis\"\n \"~/unity3d_env_local.py\": \"./unity3d_env_local.py\"\n\n# Files or directories to copy from the head node to the worker nodes. The format is a\n# list of paths. The same path on the head node will be copied to the worker node.\n# This behavior is a subset of the file_mounts behavior. In the vast majority of cases\n# you should just use file_mounts. Only use this if you know what you're doing!\ncluster_synced_files: []\n\n# Whether changes to directories in file_mounts or cluster_synced_files in the head node\n# should sync to the worker node continuously\nfile_mounts_sync_continuously: False\n\n# Patterns for files to exclude when running rsync up or rsync down\nrsync_exclude:\n - \"**/.git\"\n - \"**/.git/**\"\n\n# Pattern files to use for filtering out files when running rsync up or rsync down. The file is searched for\n# in the source directory and recursively through all subdirectories. For example, if .gitignore is provided\n# as a value, the behavior will match git's behavior for finding and using .gitignore files.\nrsync_filter:\n - \".gitignore\"\n\n# List of commands that will be run before `setup_commands`. If docker is\n# enabled, these commands will run outside the container and before docker\n# is setup.\ninitialization_commands: []\n\n# List of shell commands to run to set up nodes.\nsetup_commands: []\n # Note: if you're developing Ray, you probably want to create a Docker image that\n # has your Ray repo pre-cloned. Then, you can replace the pip installs\n # below with a git checkout (and possibly a recompile).\n # Uncomment the following line if you want to run the nightly version of ray (as opposed to the latest)\n # - pip install -U \"ray[full] @ https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl\"\n\n# Custom commands that will be run on the head node after common setup.\nhead_setup_commands: []\n\n# Custom commands that will be run on worker nodes after common setup.\nworker_setup_commands: []\n\n# Command to start ray on the head node. You don't need to change this.\nhead_start_ray_commands:\n - ray stop\n - ulimit -n 65536; ray start --head --port=6379 --object-manager-port=8076 --autoscaling-config=~/ray_bootstrap_config.yaml\n\n# Command to start ray on worker nodes. You don't need to change this.\nworker_start_ray_commands:\n - ray stop\n - ulimit -n 65536; ray start --address=$RAY_HEAD_IP:6379 --object-manager-port=8076\n\nhead_node: {}\nworker_nodes: {}", "branch": "d4c20c970b15f32d6bef7dadd2ad9e1db9b34132", "issue_url": "https://github.com/ray-project/ray/issues/14883", "fix_url": "https://github.com/ray-project/ray/pull/15049", "issue_created": "2021-03-24", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ray-15990", "system": "ray", "issue_number": "15990", "lite": false, "title": "Ray 1.3.0 CHECK fail during normal task scheduling", "description": "What is the problem?\nWhile transitioning Modin to Ray version 1.3.0 we have several tests crash in Github Actions CI. Crashes could not be reproduced in development environment until I tried to create a VM with the same specs as Github Actions run: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners\nRunning such VM with 2 CPU cores and 7GB of RAM stably reproduces these crashes.\n\nRay version and other system information (Python version, TensorFlow version, OS):\n\nRay 1.3.0. Ubuntu 20.04.2 LTS.\n\nReproduction (REQUIRED)\nI created a Vagrantfile to easily create and provision a reproducer VM:\nVagrantfile.gz\n\nTo use it follow these steps:\n\nYou need to have virtualization settings enabled in your BIOS https://bce.berkeley.edu/enabling-virtualization-in-your-pc-bios.html\nInstall vagrant from https://www.vagrantup.com/downloads\nInstall VM provider if not installed. By default vagrant uses VirtualBox.\n3.1. Install VirtualBox from https://www.virtualbox.org/wiki/Linux_Downloads\n3.2. Alternatively you can use KVM. I checked that both VMs produce the same result. To use KVM you need to install vagrant-libvirt plugin by vagrant plugin install vagrant-libvirt. It requires a bunch of dependencies which can be found here https://github.com/vagrant-libvirt/vagrant-libvirt. Also since my /var/lib filesystem is not large enough, I set up VMs to use an images pool which can be created and activated like this:\nvirsh pool-define-as images dir --target /localdisk/libvirt\nvirsh pool-start images\nAdd your user to vboxusers or libvirt group and make sure that setting is effective.\nRun vagrant up in the same directory as Vagrantfile.\nTo get to VM run vagrant ssh ubuntu2004-7gb.\nOn VM activate conda environment and run tests command line.\nThis is a stack trace that I am getting in the crash:\n\nThread 37 \"worker.io\" received signal SIGABRT, Aborted.\n[Switching to Thread 0x7fffd55fa700 (LWP 16109)]\n__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50\n50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.\n(gdb) bt\n#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50\n#1 0x00007ffff7c6d859 in __GI_abort () at abort.c:79\n#2 0x00007fffdd32bb05 in ray::SpdLogMessage::Flush() ()\n from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#3 0x00007fffdd32bb3d in ray::RayLog::~RayLog() () from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#4 0x00007fffdcf48b6c in ray::CoreWorkerDirectTaskSubmitter::RequestNewWorkerIfNeeded(std::tuple >, ray::ActorID> const&, ray::rpc::Address const*)::{lambda(ray::Status const&, ray::rpc::RequestWorkerLeaseReply const&)#1}::operator()(ray::Status const&, ray::rpc::RequestWorkerLeaseReply const&) const ()\n from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#5 0x00007fffdcf93dd5 in ray::rpc::ClientCallImpl::OnReplyReceived() ()\n from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#6 0x00007fffdce9dacb in std::_Function_handler::_M_invoke(std::_Any_data const&) () from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#7 0x00007fffdd2daa08 in boost::asio::detail::completion_handler >::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) ()\n from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#8 0x00007fffdd3e09a1 in boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&, boost::asio::detail::scheduler_thread_info&, boost::system::error_code const&) ()\n from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#9 0x00007fffdd3e0ad1 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()\n from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#10 0x00007fffdd3e25d0 in boost::asio::io_context::run() ()\n from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#11 0x00007fffdce9b895 in ray::CoreWorker::RunIOService() ()\n from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#12 0x00007fffdd685d10 in execute_native_thread_routine ()\n from /home/vagrant/miniconda3/envs/modin/lib/python3.8/site-packages/ray/_raylet.so\n#13 0x00007ffff7fa8609 in start_thread (arg=) at pthread_create.c:477\n#14 0x00007ffff7d6a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95", "branch": "55bb1e93b487cdc2e31d99db0174bf11c3a70ae8", "issue_url": "https://github.com/ray-project/ray/issues/15990", "fix_url": "https://github.com/ray-project/ray/pull/16063", "issue_created": "2021-05-03", "severity": "Critical", "root_cause_type": "Concurrency", "bug_complexity": "High", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ray-16614", "system": "ray", "issue_number": "16614", "lite": false, "title": "[Core] GPU assignment via CUDA_VISIBLE_DEVICES is broken when using placement groups with \"ray start --head\"", "description": "What is the problem?\nGPU assignment via CUDA_VISIBLE_DEVICES is broken when using placement groups.\n\nRay version and other system information (Python version, TensorFlow version, OS):\nRay 1.3.0\nTensorflow: 1.15.0\nPyTorch: 1.7.1\nOS: Linux (in docker container)\n\nReproduction (REQUIRED)\nimport ray\nfrom ray.util.placement_group import placement_group\nimport time\n\nray.init()\n\n# Create placement group with 4 bundles using 1 GPU each.\nnum_gpus = 4\nbundles = [{\"GPU\": 1, \"CPU\": 1} for _ in range(num_gpus)]\npg = placement_group(bundles)\nray.get(pg.ready())\n\n# Actor using 1 GPU that has a method to print $CUDA_VISIBLE_DEVICES env variable\n@ray.remote(num_gpus=1, num_cpus=1)\nclass Foo:\n\n def bar(self):\n import os\n print(f'CUDA_VISIBLE_DEVICES={os.environ.get(\"CUDA_VISIBLE_DEVICES\", \"\")}')\n\n# Necessary to prevent SystemErrors to occur.\ntime.sleep(5)\n\n# Create one actor per GPU and print the corresponding #CUDA_VISIBLE_DEVICES env variable.\nactors = []\nfor gpu_idx in range(num_gpus):\n ray_options = {\"placement_group\": pg, \"placement_group_bundle_index\": gpu_idx}\n actors.append(Foo.options(**ray_options).remote())\n actors[-1].bar.remote()\n\n# Necessary to prevent SystemErrors to occur.\ntime.sleep(5)\n\n# Cleanup\ndel actors\nray.util.remove_placement_group(pg)\nWhen running the above snippet on e.g. a p3.8xlarge AWS instance the GPU device assignments fail ~1 out of 5 runs and the output looks e.g. like this:\n\nCUDA_VISIBLE_DEVICES=0\nCUDA_VISIBLE_DEVICES=1,3\nCUDA_VISIBLE_DEVICES=2\nCUDA_VISIBLE_DEVICES=1,3\nI could also reproduce this with the nightly build from 22nd of June 2021.", "branch": "e1cd8580a0b4aee1fc47671b0fdfe9ea1b1a3c02", "issue_url": "https://github.com/ray-project/ray/issues/16614", "fix_url": "https://github.com/ray-project/ray/pull/17318", "issue_created": "2021-05-27", "severity": "Critical", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ray-22122", "system": "ray", "issue_number": "22122", "lite": true, "title": "[Bug] Resource demand backlog caps out at 10+ in multi-node K8s cluster", "description": "Ray Component\nRay Clusters\n\nWhat happened + What you expected to happen\nMy Setup:\n\nI have deployed a Ray Cluster on Kubernetes with EKS. The cluster has a worker type with 15 CPUs that is always on (min_workers: 1). Other worker types include 7 CPUs, 15 CPUs, 30 CPUs.\n\nI've also configured: upscaling_speed=9999, AUTOSCALER_MAX_LAUNCH_BATCH=9999, AUTOSCALER_MAX_CONCURRENT_LAUNCHES=9999 as recommended here: #21683 (comment)\n\nMain Issue:\n\nWhenever I launch 200 tasks, the autoscaler only launches a single 7-cpu worker. After that worker is ready, it launches another single 7-cpu worker. I expect it to launch at least enough workers for 185 CPUs in the first iteration.\n\nIn the Ray Operator Pod Logs, I see {'CPU': 1.0}: 1+ pending tasks/actors. I imagine this should be something like \"185+ pending tasks/actors\"?\n\nHowever, I can successfully use ray.autoscaler.sdk.request_resources to request 200 cpus all at once.\n\nRay Operator Pod Logs:\nkubectl logs -f po/ray-operator-987dc99b9-47v92 | grep Resources -A 10\n\nResources\n---------------------------------------------------------------\nUsage:\n 0.0/15.0 CPU\n 0.00/25.900 GiB memory\n 0.00/10.249 GiB object_store_memory\n\nDemands:\n (no resource demands)\npy38-cu112,karpenter:2022-02-04 10:47:45,337 DEBUG gcs_utils.py:245 -- internal_kv_put b'__autoscaling_status_legacy' b\"Cluster status: 1 nodes\\n - MostDelayedHeartbeats: {'10.16.115.16': 0.6050498485565186, '10.16.126.217': 0.6049869060516357}\\n - NodeIdleSeconds: Min=0 Mean=38219 Max=76437\\n - ResourceUsage: 0.0/15.0 CPU, 0.0 GiB/25.9 GiB memory, 0.0 GiB/10.25 GiB object_store_memory\\n - TimeSinceLastHeartbeat: Min=0 Mean=0 Max=0\\nWorker node types:\\n - wkr-15cpu30g-ondemand: 1\" True None\npy38-cu112,karpenter:2022-02-04 10:47:45,338 DEBUG legacy_info_string.py:26 -- Cluster status: 1 nodes\n--\nResources\n---------------------------------------------------------------\nUsage:\n 4.0/15.0 CPU\n 0.00/25.900 GiB memory\n 0.00/10.249 GiB object_store_memory\n\nDemands:\n {'CPU': 1.0}: 1+ pending tasks/actors\npy38-cu112,karpenter:2022-02-04 10:47:51,278 DEBUG gcs_utils.py:245 -- internal_kv_put b'__autoscaling_status_legacy' b\"Cluster status: 1 nodes\\n - MostDelayedHeartbeats: {'10.16.115.16': 0.5087563991546631, '10.16.126.217': 0.5086848735809326}\\n - NodeIdleSeconds: Min=0 Mean=0 Max=0\\n - ResourceUsage: 4.0/15.0 CPU, 0.0 GiB/25.9 GiB memory, 0.0 GiB/10.25 GiB object_store_memory\\n - TimeSinceLastHeartbeat: Min=0 Mean=0 Max=0\\nWorker node types:\\n - wkr-15cpu30g-ondemand: 1\" True None\npy38-cu112,karpenter:2022-02-04 10:47:51,289 DEBUG legacy_info_string.py:26 -- Cluster status: 1 nodes\n--\nResources\n---------------------------------------------------------------\nUsage:\n 10.0/15.0 CPU\n 0.00/25.900 GiB memory\n 0.00/10.249 GiB object_store_memory\n\nDemands:\n {'CPU': 1.0}: 1+ pending tasks/actors\npy38-cu112,karpenter:2022-02-04 10:47:57,323 DEBUG gcs_utils.py:245 -- internal_kv_put b'__autoscaling_status_legacy' b\"Cluster status: 1 nodes\\n - MostDelayedHeartbeats: {'10.16.115.16': 0.4549856185913086, '10.16.126.217': 0.4549136161804199}\\n - NodeIdleSeconds: Min=0 Mean=0 Max=0\\n - ResourceUsage: 10.0/15.0 CPU, 0.0 GiB/25.9 GiB memory, 0.0 GiB/10.25 GiB object_store_memory\\n - TimeSinceLastHeartbeat: Min=0 Mean=0 Max=0\\nWorker node types:\\n - wkr-15cpu30g-ondemand: 1\" True None\npy38-cu112,karpenter:2022-02-04 10:47:57,324 DEBUG legacy_info_string.py:26 -- Cluster status: 1 nodes\n--\nResources\n---------------------------------------------------------------\nUsage:\n 15.0/15.0 CPU\n 0.00/25.900 GiB memory\n 0.00/10.249 GiB object_store_memory\n\nDemands:\n {'CPU': 1.0}: 1+ pending tasks/actors\npy38-cu112,karpenter:2022-02-04 10:48:03,348 DEBUG gcs_utils.py:245 -- internal_kv_put b'__autoscaling_status_legacy' b\"Cluster status: 1 nodes\\n - MostDelayedHeartbeats: {'10.16.115.16': 0.54921555519104, '10.16.126.217': 0.5491447448730469}\\n - NodeIdleSeconds: Min=0 Mean=0 Max=0\\n - ResourceUsage: 15.0/15.0 CPU, 0.0 GiB/25.9 GiB memory, 0.0 GiB/10.25 GiB object_store_memory\\n - TimeSinceLastHeartbeat: Min=0 Mean=0 Max=0\\nWorker node types:\\n - wkr-15cpu30g-ondemand: 1\" True None\npy38-cu112,karpenter:2022-02-04 10:48:03,350 DEBUG legacy_info_string.py:26 -- Cluster status: 1 nodes\n--\nResources\n---------------------------------------------------------------\nUsage:\n 15.0/15.0 CPU\n 0.00/25.900 GiB memory\n 0.00/10.249 GiB object_store_memory\n\nDemands:\n {'CPU': 1.0}: 1+ pending tasks/actors\nRay Pod Description:\n\nName: ray-operator-987dc99b9-47v92\nNamespace: karpenter\nPriority: 0\nNode: ip-10-16-65-175.us-west-2.compute.internal/10.16.65.175\nStart Time: Thu, 03 Feb 2022 13:05:01 -0600\nLabels: cluster.ray.io/component=operator\n pod-template-hash=987dc99b9\nAnnotations: kubernetes.io/psp: eks.privileged\nStatus: Running\nIP: 10.16.68.93\nIPs:\n IP: 10.16.68.93\nControlled By: ReplicaSet/ray-operator-987dc99b9\nContainers:\n ray:\n Container ID: docker://f78dc8efee6c1f8483438e325c275a281c310341a1f304f4811aa8c80d263903\n Image: rayproject/ray:bbc64e\n Image ID: docker-pullable://rayproject/ray@sha256:6a0520c449555a31418ed79188827553e43276db6abc1bc4341edd16dd832eb3\n Port: \n Host Port: \n Command:\n ray-operator\n State: Running\n Started: Thu, 03 Feb 2022 13:05:03 -0600\n Ready: True\n Restart Count: 0\n Limits:\n cpu: 1\n memory: 2Gi\n Requests:\n cpu: 1\n ephemeral-storage: 1Gi\n memory: 1Gi\n Environment:\n AUTOSCALER_MAX_NUM_FAILURES: inf\n AUTOSCALER_MAX_LAUNCH_BATCH: 9999\n AUTOSCALER_MAX_CONCURRENT_LAUNCHES: 9999\n Mounts:\n /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-wq2kl (ro)\nConditions:\n Type Status\n Initialized True\n Ready True\n ContainersReady True\n PodScheduled True\nVolumes:\n kube-api-access-wq2kl:\n Type: Projected (a volume that contains injected data from multiple sources)\n TokenExpirationSeconds: 3607\n ConfigMapName: kube-root-ca.crt\n ConfigMapOptional: \n DownwardAPI: true\nQoS Class: Burstable\nNode-Selectors: \nTolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s\n node.kubernetes.io/unreachable:NoExecute op=Exists for 300s\nEvents: \nVersions / Dependencies\nRay Operator Image: rayproject/ray:bbc64e\nRay Client Version: 1.9.2\nPython 3.8\nKubernetes Version: 1.21 with EKS\n\nReproduction script\nfrom pprint import pprint\n\nimport ray\nray.init(\"ray://mycluster.internal:10001\")\n\n@ray.remote\ndef task():\n import time\n time.sleep(30)\n\npprint(ray.cluster_resources())\nresults = ray.get([task.remote() for _ in range(200)])\nAnything else\nThis issue occurs every time.\n\n", "branch": "11bbf00338b23c9c318f2d9e7b44ee49b1339043", "issue_url": "https://github.com/ray-project/ray/issues/22122", "fix_url": "https://github.com/ray-project/ray/pull/22644", "issue_created": "2022-02-08", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "High", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ray-25699", "system": "ray", "issue_number": "25699", "lite": true, "title": "[core] Idle workers from a completed job are not killed due to borrowed references", "description": "What happened + What you expected to happen\nRun following scripts; once the job finished the worker is leaked because task argument obj is still being referenced.\n\nrepro.py\n\nimport ray\nimport numpy as np\nimport tensorflow\n\ndef leak_repro(obj):\n # If import is moved here then the leak does not occur.\n # import tensorflow\n tensorflow\n return []\n\nds = ray.data.from_numpy(np.ones((100_000)))\nds.map(leak_repro)\nIDLE processes will stay active.\nimage\n\nObjects will stay pinned in memory.\n\n--- Summary for node address: 172.31.20.214 ---\nMem Used by Objects Local References Pinned Used by task Captured in Objects Actor Handles\n241198.0 B 0, (0.0 B) 2, (241198.0 B) 0, (0.0 B) 0, (0.0 B) 0, (0.0 B) \n\n--- Object references for node address: 172.31.20.214 ---\nIP Address PID Type Call Site Status Size Reference Type Object Ref \n172.31.20.214 2216 Worker (deserialize task arg) - 120599.0 B PINNED_IN_MEMORY c8ef45ccd0112571ffffffffffffffffffffffff0100000001000000\n ray.data._internal.co \n mpute._map_block_nospl \n it \n\n172.31.20.214 2215 Worker (deserialize task arg) - 120599.0 B PINNED_IN_MEMORY 16310a0f0a45af5cffffffffffffffffffffffff0100000001000000\n ray.data._internal.co \n mpute._map_block_nospl \n it \nVersions / Dependencies\nlatest ray\n\nReproduction script\nCreate repro.py and run python repro.py\n\n", "branch": "37086a5a1d0b85d7f6779d362395d5fbc59d5ad9", "issue_url": "https://github.com/ray-project/ray/issues/25699", "fix_url": "https://github.com/ray-project/ray/pull/32217", "issue_created": "2022-06-02", "severity": "Critical", "root_cause_type": "Resource leak", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 1} {"instance_id": "ray-30229", "system": "ray", "issue_number": "30229", "lite": false, "title": "[Dashboard] diskless nodes crash reporter_agent resulting in no stats", "description": "What happened + What you expected to happen\nWhen running ray on a databricks cluster, no stats appear in the dashboard.\nIn the dashboard_agent.log I see:\n\n\nTraceback (most recent call last):40 File \"/databricks/python/lib/python3.9/site-packages/ray/dashboard/modules/reporter/reporter_agent.py\", line 827, in _perform_iteration41 stats = self._get_all_stats()42 File \"/databricks/python/lib/python3.9/site-packages/ray/dashboard/modules/reporter/reporter_agent.py\", line 491, in _get_all_stats43 disk_stats = self._get_disk_io_stats()44 File \"/databricks/python/lib/python3.9/site-packages/ray/dashboard/modules/reporter/reporter_agent.py\", line 401, in _get_disk_io_stats45 stats.read_bytes,46AttributeError: 'NoneType' object has no attribute 'read_bytes\n\nthe def _get_disk_io_stats(): method in reporter_agent.py needs some sort of error handling for that rather than crashing the report for all the other stats\n\nVersions / Dependencies\nray 2.1.0\npython 3.9.5\n\nReproduction script\nstart ray with:\n\n\nray start --head --include-dashboard=true\n\non a databricks cluster and check the dashboard_agent.log", "branch": "d59f189540b14269f49d976ba60e97b804f011ba", "issue_url": "https://github.com/ray-project/ray/issues/30229", "fix_url": "https://github.com/ray-project/ray/pull/30404", "issue_created": "2022-11-12", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Low", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ray-38591", "system": "ray", "issue_number": "38591", "lite": false, "title": "[core] Possible memory leak in async actor implementation", "description": "@shrekris-anyscale and I have been trying to track down a memory leak issue happening across multiple serve components. All of them are async actors and the growth only happens when actor calls are being made, so it lines up that it could be a memory leak related to async actor calls.\n\nI ran a minimal script to send batches of many async actor calls and memory appears to be consistently growing. This is running on nightly wheels, commit sha: 0b8fd1d6dd7e83656713b21bb408fa7f04244bfb.\n\nRepro script (pinning to head node):\n\nimport ray\n\n@ray.remote\nclass A:\n async def hi(self):\n return \"hi\"\n\na = A.options(resources={\"node:10.0.62.86\": 0.1}).remote()\n\nwhile True:\n ray.get([a.hi.remote() for _ in range(10000)])\nMemory growth over 3 hours:\nScreen Shot 2023-08-17 at 5 05 49 PM\n\nLink to the workspace where this is currently running (I plan to leave it going overnight, please don't touch):\n\nhttps://console.anyscale-staging.com/o/anyscale-internal/workspaces/expwrk_czchm1deg9ecnvv44a5cnl3gq6/ses_vw8ax7ielka9scsy8m38iu2lbg\nFor reference, here is a run of the same script but dropping the async def:\n\nimport ray\n\n@ray.remote\nclass A:\n def hi(self):\n return \"hi\"\n\na = A.options(resources={\"node:10.0.62.86\": 0.1}).remote()\n\nwhile True:\n ray.get([a.hi.remote() for _ in range(10000)])\nScreen Shot 2023-08-17 at 5 06 29 PM\n\n", "branch": "449afc9461a54ddd15a2f479b163ec4daf9d12a4", "issue_url": "https://github.com/ray-project/ray/issues/38591", "fix_url": "https://github.com/ray-project/ray/pull/39210", "issue_created": "2023-08-17", "severity": "Critical", "root_cause_type": "Dependency", "bug_complexity": "High", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 9} {"instance_id": "ray-41076", "system": "ray", "issue_number": "41076", "lite": false, "title": "[Core] GCS crash if instantiating JobSubmissionClient with invalid address", "description": "What happened + What you expected to happen\nWhen instantiating a JobSubmissionClient, if an invalid address is provided, gcs will crash the entire python interpreter and throw an error:\n\n# all good\nclient = JobSubmissionClient(\"https://legitimate.address.com\")\n\n# not good...\nclient = JobSubmissionClient(\"foobar\")\nThe latter gives us a big ugly stack trace:\n\n[2023-11-10 13:42:59,990 C 74612 4407628] gcs_client.h:51: Check failed: address.size() == 2\n*** StackTrace Information ***\n0 _raylet.so 0x000000010a61dc71 _ZN3raylsERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEERKNS_10StackTraceE + 65 ray::operator<<()\n1 _raylet.so 0x000000010a64f1c2 _ZN3ray13SpdLogMessage5FlushEv + 114 ray::SpdLogMessage::Flush()\n2 _raylet.so 0x000000010a64f092 _ZN3ray13SpdLogMessageD2Ev + 18 ray::SpdLogMessage::~SpdLogMessage()\n3 _raylet.so 0x000000010a62168f _ZN3ray6RayLogD2Ev + 47 ray::RayLog::~RayLog()\n4 _raylet.so 0x0000000109b9e2d2 _ZN3ray3gcs16GcsClientOptionsC2ERKNSt3__112basic_stringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEE + 450 ray::gcs::GcsClientOptions::GcsClientOptions()\n5 _raylet.so 0x0000000109b9de1f _ZL59__pyx_pw_3ray_7_raylet_16GcsClientOptions_1from_gcs_addressP7_objectS0_ + 335 __pyx_pw_3ray_7_raylet_16GcsClientOptions_1from_gcs_address()\n6 _raylet.so 0x0000000109afe905 _ZL25__Pyx_PyObject_CallOneArgP7_objectS0_ + 101 __Pyx_PyObject_CallOneArg()\n7 _raylet.so 0x0000000109bb8f7d _ZL36__pyx_tp_new_3ray_7_raylet_GcsClientP11_typeobjectP7_objectS2_ + 701 __pyx_tp_new_3ray_7_raylet_GcsClient()\n8 libpython3.10.dylib 0x0000000105a79b0c type_call + 76 type_call\n9 libpython3.10.dylib 0x0000000105a1be88 _PyObject_MakeTpCall + 376 _PyObject_MakeTpCall\n10 libpython3.10.dylib 0x0000000105b0f4fe call_function + 974 call_function\n11 libpython3.10.dylib 0x0000000105b0bc99 _PyEval_EvalFrameDefault + 28937 _PyEval_EvalFrameDefault\n12 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n13 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n14 libpython3.10.dylib 0x0000000105b051cb _PyEval_EvalFrameDefault + 1595 _PyEval_EvalFrameDefault\n15 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n16 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n17 libpython3.10.dylib 0x0000000105b051cb _PyEval_EvalFrameDefault + 1595 _PyEval_EvalFrameDefault\n18 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n19 libpython3.10.dylib 0x0000000105a1bcb4 _PyObject_FastCallDictTstate + 260 _PyObject_FastCallDictTstate\n20 libpython3.10.dylib 0x0000000105a1c70b _PyObject_Call_Prepend + 139 _PyObject_Call_Prepend\n21 libpython3.10.dylib 0x0000000105a847b6 slot_tp_init + 214 slot_tp_init\n22 libpython3.10.dylib 0x0000000105a79c14 type_call + 340 type_call\n23 libpython3.10.dylib 0x0000000105a1be88 _PyObject_MakeTpCall + 376 _PyObject_MakeTpCall\n24 libpython3.10.dylib 0x0000000105b0f4fe call_function + 974 call_function\n25 libpython3.10.dylib 0x0000000105b051cb _PyEval_EvalFrameDefault + 1595 _PyEval_EvalFrameDefault\n26 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n27 libpython3.10.dylib 0x0000000105b049b8 PyEval_EvalCode + 120 PyEval_EvalCode\n28 libpython3.10.dylib 0x0000000105b0164b builtin_exec + 619 builtin_exec\n29 libpython3.10.dylib 0x0000000105a629a7 cfunction_vectorcall_FASTCALL + 199 cfunction_vectorcall_FASTCALL\n30 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n31 libpython3.10.dylib 0x0000000105b051cb _PyEval_EvalFrameDefault + 1595 _PyEval_EvalFrameDefault\n32 libpython3.10.dylib 0x0000000105a30133 gen_send_ex2 + 435 gen_send_ex2\n33 libpython3.10.dylib 0x0000000105b073c1 _PyEval_EvalFrameDefault + 10289 _PyEval_EvalFrameDefault\n34 libpython3.10.dylib 0x0000000105a30133 gen_send_ex2 + 435 gen_send_ex2\n35 libpython3.10.dylib 0x0000000105b073c1 _PyEval_EvalFrameDefault + 10289 _PyEval_EvalFrameDefault\n36 libpython3.10.dylib 0x0000000105a30133 gen_send_ex2 + 435 gen_send_ex2\n37 libpython3.10.dylib 0x0000000105a30347 gen_send + 23 gen_send\n38 libpython3.10.dylib 0x0000000105a2584a method_vectorcall_O + 138 method_vectorcall_O\n39 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n40 libpython3.10.dylib 0x0000000105b0bbbc _PyEval_EvalFrameDefault + 28716 _PyEval_EvalFrameDefault\n41 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n42 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n43 libpython3.10.dylib 0x0000000105b051cb _PyEval_EvalFrameDefault + 1595 _PyEval_EvalFrameDefault\n44 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n45 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n46 libpython3.10.dylib 0x0000000105b0bbbc _PyEval_EvalFrameDefault + 28716 _PyEval_EvalFrameDefault\n47 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n48 libpython3.10.dylib 0x0000000105a1e75d method_vectorcall + 205 method_vectorcall\n49 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n50 libpython3.10.dylib 0x0000000105b0bc99 _PyEval_EvalFrameDefault + 28937 _PyEval_EvalFrameDefault\n51 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n52 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n53 libpython3.10.dylib 0x0000000105b0bbbc _PyEval_EvalFrameDefault + 28716 _PyEval_EvalFrameDefault\n54 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n55 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n56 libpython3.10.dylib 0x0000000105b0bbbc _PyEval_EvalFrameDefault + 28716 _PyEval_EvalFrameDefault\n57 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n58 libpython3.10.dylib 0x0000000105b0f2de call_function + 430 call_function\n59 libpython3.10.dylib 0x0000000105b0bbbc _PyEval_EvalFrameDefault + 28716 _PyEval_EvalFrameDefault\n60 libpython3.10.dylib 0x0000000105b04a62 _PyEval_Vector + 146 _PyEval_Vector\n61 libpython3.10.dylib 0x0000000105a1e75d method_vectorcall + 205 method_vectorcall\n62 libpython3.10.dylib 0x0000000105a1c25b PyVectorcall_Call + 155 PyVectorcall_Call\n63 libpython3.10.dylib 0x0000000105b0c0cc _PyEval_EvalFrameDefault + 30012 _PyEval_EvalFrameDefault\nIdeally, this error should be caught at the Python level and raise an exception, alerting the user that the address is invalid. (I'm not positive what constitutes a valid vs invalid address, but in my tests \"legitimate\" URLs always worked and random strings never did.)\n\nVersions / Dependencies\nRay 2.8.0\nPython 3.10.6\n\nReproduction script\nimport os\nfrom ray.job_submission import JobSubmissionClient\n\n# RAY_ADDRESS always overrides user-provided address, so let's clear it\ntry:\n del(os.environ[\"RAY_ADDRESS\"])\nexcept KeyError:\n pass\n\nclient = JobSubmissionClient(address=\"foo\")\n# CRASH!", "branch": "76907c10290851a6c388d588cccb1381d714f573", "issue_url": "https://github.com/ray-project/ray/issues/41076", "fix_url": "https://github.com/ray-project/ray/pull/41253", "issue_created": "2023-11-10", "severity": "Critical", "root_cause_type": "Error handling", "bug_complexity": "Easy", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ray-46315", "system": "ray", "issue_number": "46315", "lite": false, "title": "[core] Cancelling tasks who is waiting for dependencies hangs result objects", "description": "What happened + What you expected to happen\nWhen you have a task returning a Ray Object, and the task is in \"waiting dependencies\" status; and you do ray.cancel(ref) on the ref. You expect the next ray.get(ref) raises TaskCancelledError but it hangs now.\n\nThis issue also applies for streaming generators, and when the task is resubmitted via lineage reconstruction.\n\nThis comes from\n\nray/src/ray/core_worker/transport/direct_task_transport.cc\n\nLines 798 to 799 in 755a49b\n\n // This case is reached for tasks that have unresolved dependencies. \n // No executing tasks, so cancelling is a noop. \nwhere if a task being cancelled have unresolved deps, it does noop.\n\nThis may be true in 4 yrs ago, but now we need to fail the task and mark all objects as failed with the exception.\n\nVersions / Dependencies\nmaster\n\nReproduction script\nRun this script multiple times, it's 70% hanging and 30% passing.\n\nimport ray\nimport numpy as np\nimport pytest\nfrom ray._private.test_utils import SignalActor\nimport time\n\ndef test_cancel_pending_arg_running():\n with ray.init():\n @ray.remote(max_retries=-1)\n def wait_forever():\n print(\"wait_and_reset starting\")\n while True:\n time.sleep(10000)\n\n @ray.remote(max_retries=-1)\n def has_deps(may_block):\n big = may_block\n return big * 2\n\n may_block = wait_forever.remote()\n ref = has_deps.remote(may_block)\n print(f\"{ref=}\")\n \n ready, not_ready = ray.wait([may_block, ref], timeout=1)\n assert not ready\n assert len(not_ready) == 2\n print(f\"both are not ready: {may_block=}, {ref=}\")\n\n # Now, the generator is pending arg. Cancel it.\n print(\"Cancelling\")\n ray.cancel(ref)\n\n print(\"Getting\")\n with pytest.raises(ray.exceptions.TaskCancelledError):\n ray.get(ref) # This should raise TaskCancelledError, but hangs\n\n\nif __name__ == \"__main__\":\n import os,sys\n\n if os.environ.get(\"PARALLEL_CI\"):\n sys.exit(pytest.main([\"-n\", \"auto\", \"--boxed\", \"-vs\", __file__]))\n else:\n sys.exit(pytest.main([\"-sv\", __file__]))", "branch": "a1d4cb19ffcf3e430f88d2e00504b930fadad338", "issue_url": "https://github.com/ray-project/ray/issues/46315", "fix_url": "https://github.com/ray-project/ray/pull/48661", "issue_created": "2024-06-28", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ray-47668", "system": "ray", "issue_number": "47668", "lite": false, "title": "[UI] When a Ray worker node dies, it makes Ray dashboard cluster page and logs page broken", "description": "What happened + What you expected to happen\nWhen a Ray worker node dies, it makes Ray dashboard \"cluster\" page and \"logs\" page broken\n\nNormal \"cluster page\" containing dead node should be like:\nimage\n\nBut now it becomes:\nimage\n\nand when Ray worker node dies, \"logs\" page is completely broken and show nothing.\n\nVersions / Dependencies\nThis bug is introduced in Ray nightly build version , Ray 2.35 version is good.\n\nReproduction script\ninstall Ray nightly build version\nstart a Ray head node like:\nray start --head --node-ip-address=127.0.0.1 --port 9988 --dashboard-host=0.0.0.0\nstart a Ray worker node like:\nray start --address 127.0.0.1:9988 --block &\nFind the Ray worker node processes group, and kill (-9) all processes in the group\nps -ef|grep \"ray start --address 127.0.0.1:9988\" # Get process id of \"ray start --address 127.0.0.1:9988\" command\nkill -9 -{xxx} # kill the process **group** of id printed in above command\nWait a few seconds, Open Ray dashboard cluster page. error occurs.\nChecking nodes?view=summary request response, it got error like:\n\nTraceback (most recent call last):\n File \"/local_disk0/.ephemeral_nfs/envs/pythonEnv-8ac7e00d-2d10-430a-b39d-ad4447d3a5ed/lib/python3.11/site-packages/ray/dashboard/optional_utils.py\", line 224, in _update_cache\n response = task.result()\n ^^^^^^^^^^^^^\n File \"/local_disk0/.ephemeral_nfs/envs/pythonEnv-8ac7e00d-2d10-430a-b39d-ad4447d3a5ed/lib/python3.11/site-packages/ray/dashboard/modules/node/node_head.py\", line 364, in get_all_nodes\n all_node_summary, nodes_logical_resources = await asyncio.gather(\n ^^^^^^^^^^^^^^^^^^^^^\n File \"/local_disk0/.ephemeral_nfs/envs/pythonEnv-8ac7e00d-2d10-430a-b39d-ad4447d3a5ed/lib/python3.11/site-packages/ray/dashboard/datacenter.py\", line 171, in get_all_node_summary\n return [\n ^\n File \"/local_disk0/.ephemeral_nfs/envs/pythonEnv-8ac7e00d-2d10-430a-b39d-ad4447d3a5ed/lib/python3.11/site-packages/ray/dashboard/datacenter.py\", line 172, in \n await DataOrganizer.get_node_info(node_id, get_summary=True)\n File \"/local_disk0/.ephemeral_nfs/envs/pythonEnv-8ac7e00d-2d10-430a-b39d-ad4447d3a5ed/lib/python3.11/site-packages/ray/dashboard/datacenter.py\", line 150, in get_node_info\n node_info[\"status\"] = node[\"stateSnapshot\"][\"state\"]\n ~~~~^^^^^^^^^^^^^^^^^\n File \"/local_disk0/.ephemeral_nfs/envs/pythonEnv-8ac7e00d-2d10-430a-b39d-ad4447d3a5ed/lib/python3.11/site-packages/ray/dashboard/utils.py\", line 435, in __getitem__\n proxy = self._proxy[item] = make_immutable(self._dict[item])\n ~~~~~~~~~~^^^^^^\nKeyError: 'stateSnapshot'", "branch": "c1e7c45f58c659132c56815b179e9493663fe73c", "issue_url": "https://github.com/ray-project/ray/issues/47668", "fix_url": "https://github.com/ray-project/ray/pull/47701", "issue_created": "2024-09-16", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 4} {"instance_id": "ray-54830", "system": "ray", "issue_number": "54830", "lite": false, "title": "Ray Serve: Concurrency issue with llm_serve_telemetry actor", "description": "What happened + What you expected to happen\nThe Bug\nWhen starting a ray serve application with\nserve run --blocking --address $IP_HEAD $serve_config > my_log.log 2>&1 &\nI sometimes run in the error ValueError: Actor with name 'llm_serve_telemetry' already exists in the namespace llm_serve_telemetry. My guess is due to concurrently starting models, two models see there is no llm_serve_telemetry actor and both attempt to create one. As one is faster, the other raises this error. Could that be?\n\nThe deployment crashed and has to be restarted.\n\nExpected Behavior\nAll initial replicas of a model can be started in parallel.\n\nUseful Information\n\nray serve config:\n\nhttp_options: \n port: 8001\nlogging_config:\n enable_access_log: false\n log_level: \"WARNING\"\napplications:\n- name: augment_ray_serve_app\n import_path: ray.serve.llm:build_openai_app\n route_prefix: \"/\"\n args:\n llm_configs:\n - model_loading_config:\n model_id: \"augmenter\"\n model_source: \"Qwen/Qwen3-30B-A3B\"\n deployment_config:\n autoscaling_config:\n target_ongoing_requests: 2\n upscale_delay_s: 2\n downscale_delay_s: 600\n initial_replicas: 14 # 28 GPUs\n min_replicas: 1\n max_replicas: 16 # 32 GPUs\n runtime_env:\n env_vars:\n VLLM_USE_V1: \"1\"\n engine_kwargs:\n tensor_parallel_size: 2\n pipeline_parallel_size: 1\n gpu_memory_utilization: 0.9\n dtype: \"auto\"\n max_num_seqs: 40\n max_model_len: 16384 # no yarn max: 32768, 16384, 8192, \n enable_chunked_prefill: true\n enable_prefix_caching: true\n trust_remote_code: true\n tokenizer: \"/work_dir/pipeline/src/datadistill/explore/qwen3\"\n - model_loading_config:\n model_id: \"web_search_simulator\"\n model_source: \"Alibaba-NLP/Simulation_LLM_google_14B_V2\"\n deployment_config:\n autoscaling_config:\n target_ongoing_requests: 2\n upscale_delay_s: 2\n downscale_delay_s: 600\n initial_replicas: 4 # 4 GPUs\n min_replicas: 1\n max_replicas: 32 # 32 GPUs\n engine_kwargs:\n tensor_parallel_size: 1\n pipeline_parallel_size: 1\n gpu_memory_utilization: 0.9\n dtype: \"auto\"\n max_num_seqs: 40\n max_model_len: 32768\n enable_chunked_prefill: true\n enable_prefix_caching: true\n trust_remote_code: true\n- name: wiki_search_app\n import_path: wikipedia.server:app_builder \n route_prefix: /wiki\n deployments:\n - name: \"WikiSearchDeployment\"\n ray_actor_options:\n num_cpu: 1\n # while with 0.5 it works (only a few MiB are taken), it blocks an entire GPU, as build_openai_app above\n # does not support fractional GPUs\n num_gpus: 0 \nray serve log:\n\n\n================ Ray Serve Status at Tue Jul 22 18:17:11 CEST 2025 ================\nproxies:\n f9ecb4be3d77ad15b3ded3bc9a5d92f51c149ae3f25a29e835d0b928: HEALTHY\n cf8f4fd4b2aca3f08246c21f5e8cabd4cff4d5c628f2b0048ae89fb4: HEALTHY\napplications:\n augment_ray_serve_app:\n status: DEPLOYING\n message: ''\n last_deployed_time_s: 1753199985.1827998\n deployments:\n LLMDeploymentaugmenter:\n status: UPDATING\n status_trigger: CONFIG_UPDATE_STARTED\n replica_states:\n STARTING: 14\n message: |-\n A replica failed to start with exception. Retrying 19 more time(s). Error:\n ray::ServeReplica:augment_ray_serve_app:LLMDeploymentaugmenter.initialize_and_get_metadata() (pid=1743742, ip=10.6.1.6, actor_id=05385f231eb19dbf60d3d87001000000, repr=)\n File \"/lib/gcc-8.5.0/python-3.11.7-ziwh63aulhhzxksf42k5u3gnim2rbpmp/lib/python3.11/concurrent/futures/_base.py\", line 449, in result\n return self.__get_result()\n ^^^^^^^^^^^^^^^^^^^\n File \"/lib/gcc-8.5.0/python-3.11.7-ziwh63aulhhzxksf42k5u3gnim2rbpmp/lib/python3.11/concurrent/futures/_base.py\", line 401, in __get_result\n raise self._exception\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/serve/_private/replica.py\", line 1010, in initialize_and_get_metadata\n await self._replica_impl.initialize(deployment_config)\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/serve/_private/replica.py\", line 729, in initialize\n raise RuntimeError(traceback.format_exc()) from None\n RuntimeError: Traceback (most recent call last):\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/llm/_internal/serve/observability/usage_telemetry/usage.py\", line 192, in _get_or_create_telemetry_agent\n telemetry_agent = ray.get_actor(\n ^^^^^^^^^^^^^^\n ^^^^^^^^^^^^^^^^^^^\n ^^^^^^^^^^^^^^^^^^^^^\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"python/ray/includes/common.pxi\", line 87, in ray._raylet.check_status\n ValueError: Failed to look up actor with name 'llm_serve_telemetry'. This could because 1. You are trying to look up a named actor you didn't create. 2. The named actor died. 3. You did not use a namespace matching the namespace of the actor.\n\n During handling of the above exception, another exception occurred:\n\n ray::ServeReplica:augment_ray_serve_app:LLMDeploymentaugmenter.initialize_and_get_metadata() (pid=1743742, ip=10.6.1.6, actor_id=05385f231eb19dbf60d3d87001000000, repr=)\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/serve/_private/replica.py\", line 702, in initialize\n self._user_callable_asgi_app = await asyncio.wrap_future(\n ^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/serve/_private/replica.py\", line 1427, in initialize_callable\n await self._call_func_or_gen(\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/serve/_private/replica.py\", line 1373, in _call_func_or_gen\n result = await result\n ^^^^^^^^^^^^\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/llm/_internal/serve/deployments/llm/llm_server.py\", line 442, in __init__\n await asyncio.wait_for(self._start_engine(), timeout=ENGINE_START_TIMEOUT_S)\n File \"/lib/gcc-8.5.0/python-3.11.7-ziwh63aulhhzxksf42k5u3gnim2rbpmp/lib/python3.11/asyncio/tasks.py\", line 489, in wait_for\n return fut.result()\n ^^^^^^^^^^^^\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/llm/_internal/serve/deployments/llm/llm_server.py\", line 494, in _start_engine\n push_telemetry_report_for_all_models(all_models=[self._llm_config])\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/llm/_internal/serve/observability/usage_telemetry/usage.py\", line 300, in push_telemetry_report_for_all_models\n _push_telemetry_report(telemetry_model)\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/llm/_internal/serve/observability/usage_telemetry/usage.py\", line 211, in _push_telemetry_report\n telemetry_agent = _get_or_create_telemetry_agent()\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/llm/_internal/serve/observability/usage_telemetry/usage.py\", line 204, in _get_or_create_telemetry_agent\n ).remote()\n ^^^^^^^^\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/actor.py\", line 891, in remote\n return actor_cls._remote(args=args, kwargs=kwargs, **updated_options)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n ^^^^^^^^^^^^^^^^^^^\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/work_dir/pipeline/.venv/lib/python3.11/site-packages/ray/actor.py\", line 1229, in _remote\n actor_id = worker.core_worker.create_actor(\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"python/ray/includes/common.pxi\", line 77, in ray._raylet.check_status\n ValueError: Actor with name 'llm_serve_telemetry' already exists in the namespace llm_serve_telemetry\n LLMDeploymentweb_search_simulator:\n status: UPDATING\n status_trigger: CONFIG_UPDATE_STARTED\n replica_states:\n STARTING: 4\n message: 'Deployment ''LLMDeploymentweb_search_simulator'' in application\n ''augment_ray_serve_app'' has 4 replicas that have taken more than 30s to\n be scheduled. This may be due to waiting for the cluster to auto-scale or\n for a runtime environment to be installed. Resources required for each replica:\n [{\"CPU\": 1.0}, {\"GPU\": 1.0}], total resources available: {}. Use `ray status`\n for more details.'\n LLMRouter:\n status: UPDATING\n status_trigger: CONFIG_UPDATE_STARTED\n replica_states:\n STARTING: 36\n message: |-\n Deployment 'LLMRouter' in application 'augment_ray_serve_app' has 36 replicas that have taken more than 30s to initialize.\n This may be caused by a slow __init__ or reconfigure method.\n wiki_search_app:\n status: RUNNING\n message: ''\n last_deployed_time_s: 1753199985.1827998\n deployments:\n WikiSearchDeployment:\n status: HEALTHY\n status_trigger: CONFIG_UPDATE_COMPLETED\n replica_states:\n RUNNING: 1\n message: ''\ntarget_capacity: null\nlogs before the error occours:\n\n�[36m(RayWorkerWrapper pid=495986, ip=10.6.1.10)�[0m \nLoading safetensors checkpoint shards: 94% Completed | 15/16 [11:05<00:43, 43.27s/it]\n�[36m(RayWorkerWrapper pid=495988, ip=10.6.1.10)�[0m \nLoading safetensors checkpoint shards: 94% Completed | 15/16 [11:05<00:43, 43.27s/it]\n�[36m(ServeController pid=1739868)�[0m WARNING 2025-07-22 18:16:24,136 controller 1739868 -- Deployment 'LLMRouter' in application 'augment_ray_serve_app' has 36 replicas that have taken more than 30s to initialize.\n�[36m(ServeController pid=1739868)�[0m This may be caused by a slow __init__ or reconfigure method.\n�[36m(ServeReplica:augment_ray_serve_app:LLMDeploymentaugmenter pid=493848, ip=10.6.1.10)�[0m �[36m(RayWorkerWrapper pid=495986)�[0m \nLoading safetensors checkpoint shards: 94% Completed | 15/16 [11:05<00:43, 43.27s/it]�[32m [repeated 2x across cluster]�[0m\n�[36m(ServeController pid=1739868)�[0m WARNING 2025-07-22 18:16:24,246 controller 1739868 -- Deployment 'LLMDeploymentaugmenter' in application 'augment_ray_serve_app' has 10 replicas that have taken more than 30s to be scheduled. This may be due to waiting for the cluster to auto-scale or for a runtime environment to be installed. Resources required for each replica: [{\"CPU\": 1.0}, {\"GPU\": 1.0}, {\"GPU\": 1.0}], total resources available: {}. Use `ray status` for more details.\n�[36m(ServeController pid=1739868)�[0m WARNING 2025-07-22 18:16:24,246 controller 1739868 -- Deployment 'LLMDeploymentaugmenter' in application 'augment_ray_serve_app' has 4 replicas that have taken more than 30s to initialize.\n�[36m(ServeController pid=1739868)�[0m This may be caused by a slow __init__ or reconfigure method.\n�[36m(ServeController pid=1739868)�[0m WARNING 2025-07-22 18:16:24,247 controller 1739868 -- Deployment 'LLMDeploymentweb_search_simulator' in application 'augment_ray_serve_app' has 4 replicas that have taken more than 30s to be scheduled. This may be due to waiting for the cluster to auto-scale or for a runtime environment to be installed. Resources required for each replica: [{\"CPU\": 1.0}, {\"GPU\": 1.0}], total resources available: {}. Use `ray status` for more details.\n�[36m(RayWorkerWrapper pid=495986, ip=10.6.1.10)�[0m \n�[36m(RayWorkerWrapper pid=495986, ip=10.6.1.10)�[0m \nLoading safetensors checkpoint shards: 100% Completed | 16/16 [11:47<00:00, 44.25s/it]�[32m [repeated 2x across cluster]�[0m\n�[36m(RayWorkerWrapper pid=495988, ip=10.6.1.10)�[0m \n�[36m(ServeReplica:augment_ray_serve_app:LLMDeploymentaugmenter pid=493849, ip=10.6.1.10)�[0m �[36m(RayWorkerWrapper pid=495988)�[0m \n�[36m(ServeReplica:augment_ray_serve_app:LLMDeploymentaugmenter pid=493848, ip=10.6.1.10)�[0m �[36m(RayWorkerWrapper pid=495986)�[0m \n�[36m(ServeController pid=1739868)�[0m WARNING 2025-07-22 18:16:54,231 controller 1739868 -- Deployment 'LLMRouter' in application 'augment_ray_serve_app' has 36 replicas that have taken more than 30s to initialize.\n�[36m(ServeController pid=1739868)�[0m This may be caused by a slow __init__ or reconfigure method.\n�[36m(ServeController pid=1739868)�[0m WARNING 2025-07-22 18:16:54,342 controller 1739868 -- Deployment 'LLMDeploymentaugmenter' in application 'augment_ray_serve_app' has 10 replicas that have taken more than 30s to be scheduled. This may be due to waiting for the cluster to auto-scale or for a runtime environment to be installed. Resources required for each replica: [{\"CPU\": 1.0}, {\"GPU\": 1.0}, {\"GPU\": 1.0}], total resources available: {}. Use `ray status` for more details.\n�[36m(ServeController pid=1739868)�[0m WARNING 2025-07-22 18:16:54,342 controller 1739868 -- Deployment 'LLMDeploymentaugmenter' in application 'augment_ray_serve_app' has 4 replicas that have taken more than 30s to initialize.\n�[36m(ServeController pid=1739868)�[0m This may be caused by a slow __init__ or reconfigure method.\n�[36m(ServeController pid=1739868)�[0m WARNING 2025-07-22 18:16:54,343 controller 1739868 -- Deployment 'LLMDeploymentweb_search_simulator' in application 'augment_ray_serve_app' has 4 replicas that have taken more than 30s to be scheduled. This may be due to waiting for the cluster to auto-scale or for a runtime environment to be installed. Resources required for each replica: [{\"CPU\": 1.0}, {\"GPU\": 1.0}], total resources available: {}. Use `ray status` for more details.\n�[36m(ServeController pid=1739868)�[0m ERROR 2025-07-22 18:17:11,159 controller 1739868 -- Exception in Replica(id='7p8lb1qc', deployment='LLMDeploymentaugmenter', app='augment_ray_serve_app'), the replica will be stopped.\nVersions / Dependencies\n[project]\ndependencies = [\n\"accelerate>=1.8.1\",\n\"botocore>=1.38.46\",\n\"click>=8.2.1\",\n\"datasets\",\n\"dependency-injector>=4.47.1\",\n\"fastapi>=0.115.12\",\n\"omegaconf>=2.3.0\",\n\"openai[aiohttp]>=1.92.2\",\n\"orjson>=3.10.18\",\n\"peft>=0.15.2\",\n\"pydantic>=2.11.5\",\n\"pyyaml>=6.0.2\",\n\"ray[serve,llm]\",\n\"requests>=2.32.3\",\n\"shortuuid>=1.0.13\",\n\"streamlit>=1.47.0\",\n\"tenacity>=9.1.2\",\n\"trl>=0.19.0\",\n\"wandb>=0.21.0\",\n\"vllm==0.8.5.post1\",\n]\n\nWith ray version: ray 2.47.1\n\nReproduction script\nconfig.yaml:\n\nhttp_options: \n port: 8001\nlogging_config:\n enable_access_log: false\n log_level: \"WARNING\"\napplications:\n- name: augment_ray_serve_app\n import_path: ray.serve.llm:build_openai_app\n route_prefix: \"/\"\n args:\n llm_configs:\n - model_loading_config:\n model_id: \"augmenter\"\n model_source: \"Qwen/Qwen3-30B-A3B\"\n deployment_config:\n autoscaling_config:\n target_ongoing_requests: 2\n upscale_delay_s: 2\n downscale_delay_s: 600\n initial_replicas: 14 # 28 GPUs\n min_replicas: 1\n max_replicas: 16 # 32 GPUs\n runtime_env:\n env_vars:\n VLLM_USE_V1: \"1\"\n engine_kwargs:\n tensor_parallel_size: 2\n pipeline_parallel_size: 1\n gpu_memory_utilization: 0.9\n dtype: \"auto\"\n max_num_seqs: 40\n max_model_len: 16384 # no yarn max: 32768, 16384, 8192, \n enable_chunked_prefill: true\n enable_prefix_caching: true\n trust_remote_code: true\n - model_loading_config:\n model_id: \"web_search_simulator\"\n model_source: \"Alibaba-NLP/Simulation_LLM_google_14B_V2\"\n deployment_config:\n autoscaling_config:\n target_ongoing_requests: 2\n upscale_delay_s: 2\n downscale_delay_s: 600\n initial_replicas: 4 # 4 GPUs\n min_replicas: 1\n max_replicas: 32 # 32 GPUs\n engine_kwargs:\n tensor_parallel_size: 1\n pipeline_parallel_size: 1\n gpu_memory_utilization: 0.9\n dtype: \"auto\"\n max_num_seqs: 40\n max_model_len: 32768\n enable_chunked_prefill: true\n enable_prefix_caching: true\n trust_remote_code: true\nserve run --blocking config.yaml\n\n", "branch": "4c6993ee347e3a4d1ff9a26fb3daddd9bf50783c", "issue_url": "https://github.com/ray-project/ray/issues/54830", "fix_url": "https://github.com/ray-project/ray/pull/55558", "issue_created": "2025-07-22", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ray-54841", "system": "ray", "issue_number": "54841", "lite": false, "title": "[data] Failed to submit task to actor after ray.shutdown() and re-ray.init() in data pipeline for an existing cluster", "description": "What happened + What you expected to happen\nIf we have an existing ray cluster (e.g. setup using cli ray start --num-cpus 64) and we run two Ray Data pipelines back to back - each pipeline using ray.init(), processing a dataset with map_batches, and followed by ray.shutdown() - the second pipeline fails with an error indicating Ray cannot submit a task to an actor because it \"can't find actor ... it might be dead or it's from a different cluster.\"\n\nThe use case is that we want a cluster to be instantiated independent of our pipelines, and each of our pipelines might be executed one after the other (with possibly different environment variables, so you can imagine the second pipeline sepcifies runtime_env={\"env_vars\": {\"XYZ\": \"VALUE\"}} while the first doesn't)\n\nVersions / Dependencies\n('2.48.0', '03491225d59a1ffde99c3628969ccf456be13efd')\n\nReproduction script\nimport os\n\nimport ray\n\n# start a ray cluster using `ray start`\nos.environ[\"RAY_ADDRESS\"] = \"127.0.0.1:8265\"\n\n\nclass F:\n def __call__(self, x):\n return x\n\n# First pipeline\nray.init(ignore_reinit_error=True)\nray.data.range(1000).map_batches(F, concurrency=(1, 4), num_cpus=1,).take_all()\nray.shutdown()\n\n# Second pipeline\nray.init(ignore_reinit_error=True)\nray.data.range(1000).map_batches(F, concurrency=(1, 4), num_cpus=1,).take_all()\nray.shutdown()\nError\n2025-07-22 21:34:22,645\tERROR exceptions.py:73 -- Exception occurred in Ray Data or Ray Core internal code. If you continue to see this error, please open an issue on the Ray project GitHub page with the full stack trace below: https://github.com/ray-project/ray/issues/new/choose\n2025-07-22 21:34:22,645\tERROR exceptions.py:81 -- Full stack trace:\nTraceback (most recent call last):\n File \"/conda_env/lib/python3.12/site-packages/ray/data/exceptions.py\", line 49, in handle_trace\n return fn(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^\n File \"/conda_env/lib/python3.12/site-packages/ray/data/_internal/plan.py\", line 439, in execute_to_iterator\n bundle_iter = execute_to_legacy_bundle_iterator(executor, self)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/conda_env/lib/python3.12/site-packages/ray/data/_internal/execution/legacy_compat.py\", line 55, in execute_to_legacy_bundle_iterator\n bundle_iter = executor.execute(dag, initial_stats=stats)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/conda_env/lib/python3.12/site-packages/ray/data/_internal/execution/streaming_executor.py\", line 159, in execute\n StatsManager.register_dataset_to_stats_actor(\n File \"/conda_env/lib/python3.12/site-packages/ray/data/_internal/stats.py\", line 790, in register_dataset_to_stats_actor\n self._stats_actor().register_dataset.remote(\n File \"/conda_env/lib/python3.12/site-packages/ray/actor.py\", line 676, in remote\n return self._remote(args, kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/conda_env/lib/python3.12/site-packages/ray/_private/auto_init_hook.py\", line 22, in auto_init_wrapper\n return fn(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^\n File \"/conda_env/lib/python3.12/site-packages/ray/util/tracing/tracing_helper.py\", line 422, in _start_span\n return method(self, args, kwargs, *_args, **_kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/conda_env/lib/python3.12/site-packages/ray/actor.py\", line 856, in _remote\n obj_ref = invocation(args, kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/conda_env/lib/python3.12/site-packages/ray/actor.py\", line 836, in invocation\n return dst_actor._actor_method_call(\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/conda_env/lib/python3.12/site-packages/ray/actor.py\", line 2059, in _actor_method_call\n object_refs = worker.core_worker.submit_actor_task(\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"python/ray/_raylet.pyx\", line 3992, in ray._raylet.CoreWorker.submit_actor_task\n File \"python/ray/_raylet.pyx\", line 4053, in ray._raylet.CoreWorker.submit_actor_task\nException: Failed to submit task to actor ActorID(4264d583dfdde28efb09616901000000) due to b\"Can't find actor 4264d583dfdde28efb09616901000000. It might be dead or it's from a different cluster\"\n\nLooking at the traceback and then the code it seems like the StatsActor is pinned to the driver node, so even though ray shutdown kills the actor, the subsequent ray.data pipeline tries to use it again but that actor doesn't exist anymore\n\nray/python/ray/data/_internal/stats.py\n\nLines 576 to 593 in 753a275\n def _get_or_create_stats_actor(): \n ctx = DataContext.get_current() \n scheduling_strategy = ctx.scheduling_strategy \n if not ray.util.client.ray.is_connected(): \n # Pin the stats actor to the local node \n # so it fate-shares with the driver. \n scheduling_strategy = NodeAffinitySchedulingStrategy( \n ray.get_runtime_context().get_node_id(), \n soft=False, \n ) \n with _stats_actor_lock: \n return _StatsActor.options( \n name=STATS_ACTOR_NAME, \n namespace=STATS_ACTOR_NAMESPACE, \n get_if_exists=True, \n lifetime=\"detached\", \n scheduling_strategy=scheduling_strategy, \n ).remote() \n", "branch": "cf3f3ed51c3ae1e2c191a4ddcde09a5d726b8517", "issue_url": "https://github.com/ray-project/ray/issues/54841", "fix_url": "https://github.com/ray-project/ray/pull/55163", "issue_created": "2025-07-22", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ray-60453", "system": "ray", "issue_number": "60453", "lite": false, "title": "[data] Actor's shutdown hook isn't being called", "description": "What happened + What you expected to happen\nIt seem like Ray Data does not call the Actor shutdown hook, which I'd expect it to do.\n\nVersions / Dependencies\nray==2.53.0\n\nReproduction script\nimport os\n\nimport tempfile\nfrom pathlib import Path\n\nimport ray\n\nlog_file = Path(tempfile.mkdtemp()) / \"log.txt\"\n\nclass Actor:\n def __init__(self, path: str):\n self.path = path\n with open(path, \"a\") as f:\n f.write(\"init\\n\")\n\n def __call__(self, row):\n with open(self.path, \"a\") as f:\n f.write(f\"call {row}\\n\")\n return row\n\n def __del__(self):\n with open(self.path, \"a\") as f:\n f.write(\"__del__\\n\")\n\n def __ray_shutdown__(self):\n with open(self.path, \"a\") as f:\n f.write(\"__ray_shutdown__\\n\")\n\nray.init(num_cpus=2)\nray.data.from_items([1, 2, 3]).map(\n Actor,\n compute=ray.data.ActorPoolStrategy(min_size=1, max_size=1),\n fn_constructor_kwargs={\"path\": str(log_file)},\n).materialize()\n\nprint(\"after materialize:\", log_file.read_text())\nray.shutdown()\nprint(\"after shutdown:\", log_file.read_text())\noutputs:\n\n✔️ Dataset dataset_2_0 execution finished in 1.63 seconds: 100%|███████████████████| 3.00/3.00 [00:01<00:00, 1.86 row/s] \n- Map(Actor): Tasks: 0; Actors: 1 (running=0, restarting=0, pending=1); Queued blocks: 3 (0.0B); Resources: 0.0 CPU, 0.0B- Map(Actor): Tasks: 0; Actors: 0; Queued blocks: 0 (0.0B); Resources: 1.0 CPU, 8.0B object store; [all objects local]: :- Map(Actor): Tasks: 0; Actors: 0; Queued blocks: 0 (0.0B); Resources: 1.0 CPU, 8.0B object store; [all objects local]: 1\nafter materialize: init\ncall {'item': 1}\ncall {'item': 2}\ncall {'item': 3}\n\nafter shutdown: init\ncall {'item': 1}\ncall {'item': 2}\ncall {'item': 3}\nno traces of neither __ray_shutdown__ not __del__ methods being called.\n\n", "branch": "f996fa05bbbf6cbef6a80121c8c04fdf4d8f28d8", "issue_url": "https://github.com/ray-project/ray/issues/60453", "fix_url": "https://github.com/ray-project/ray/pull/61700", "issue_created": "2026-01-23", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ray-60991", "system": "ray", "issue_number": "60991", "lite": false, "title": "[core] ray.init() on nightly fails on shared machines with multiple clusters due to race condition (regression from 2.53)", "description": "What happened + What you expected to happen\nStart Cluster A (using ray start --head --port XYZ --temp-dir /tmp/a --block)\nStart Cluster B using (ray start --head --port ABC --temp-dir /tmp/b --block)\nset os.environ[\"RAY_ADDRESS\"] = \"ip:ABC\" (that of cluster B)\nrun ray.init(), should error out\nIt's my understanding that he call chain during ray.init(connect_only=True) (in above case for cluster B) will do the following\n\nray/_private/node.py → get_node_to_connect_for_driver()\nray/_private/services.py → find_node_ids() scans ALL raylets via psutil (we'll also get that of cluster A)\nReturns foreign node IDs (target cluster's raylet hasn't registered yet)\nQueries target GCS with foreign IDs → RuntimeError: No node info found\nVersions / Dependencies\nWorks on 2.53 fails on currently nightly (`)\n\nReproduction script\n# Ray 3.0 — FAILS\ndocker run --rm -v ./repro.py:/repro.py python:3.12 bash -c '\npip install -q psutil \"ray[default] @ https://s3-us-west-2.amazonaws.com/ray-wheels/master/5eb941349d3ba64287a6d2461656681f0edbf39b/ray-3.0.0.dev0-cp312-cp312-manylinux2014_x86_64.whl\"\npython /repro.py\nOutput is\n\n\nRay 3.0.0.dev0\nCluster A: fully ready\nCluster B: GCS ready (raylet still starting)\nFAIL: ConnectionError:\n# Ray 2.53 — PASSES\ndocker run --rm -v ./repro.py:/repro.py python:3.12 bash -c '\npip install -q psutil \"ray[default]==2.53.0\"\npython /repro.py\nOutput is\n\nRay 2.53.0\nCluster A: fully ready\nCluster B: GCS ready (raylet still starting)\nPASS: connected (1 nodes)\n# repro.py\n\"\"\"ray.init() race condition: find_node_ids() picks up foreign raylets before ours starts.\"\"\"\nimport os, signal, socket, subprocess, sys, time\nimport ray\nfrom ray._raylet import GcsClient\n\nIP = socket.gethostbyname(socket.gethostname())\n\ndef start_cluster(port, temp, dp, mp):\n return subprocess.Popen(\n [\"ray\", \"start\", \"--head\", \"--node-ip-address\", IP, \"--port\", str(port),\n \"--metrics-export-port\", str(mp), \"--dashboard-host\", \"127.0.0.1\",\n \"--dashboard-port\", str(dp), \"--temp-dir\", temp,\n \"--disable-usage-stats\", \"--num-cpus\", \"2\", \"--block\"],\n stdout=subprocess.PIPE, stderr=subprocess.PIPE, start_new_session=True)\n\ndef wait_gcs(addr, timeout=30):\n for _ in range(timeout):\n try:\n GcsClient(address=addr).internal_kv_get(b\"x\", None)\n return True\n except Exception:\n time.sleep(1)\n return False\n\ndef stop(proc):\n try:\n os.killpg(os.getpgid(proc.pid), signal.SIGKILL)\n proc.wait(timeout=5)\n except Exception:\n pass\n\ndef main():\n print(f\"Ray {ray.__version__}\")\n pa = pb = None\n try:\n # Cluster A: another user's cluster (fully ready)\n pa = start_cluster(6379, \"/tmp/ray_a\", 8265, 8080)\n assert wait_gcs(f\"{IP}:6379\"), \"Cluster A GCS failed\"\n print(\"Cluster A: fully ready\")\n\n # Cluster B: our cluster — wait for GCS only, NOT raylet\n pb = start_cluster(6380, \"/tmp/ray_b\", 8266, 8081)\n assert wait_gcs(f\"{IP}:6380\"), \"Cluster B GCS failed\"\n print(\"Cluster B: GCS ready (raylet still starting)\")\n\n # Connect immediately — exactly what happens when ray.init()\n # is called before the raylet has registered\n os.environ[\"RAY_ADDRESS\"] = f\"{IP}:6380\"\n try:\n ray.init(ignore_reinit_error=True)\n print(f\"PASS: connected ({len(ray.nodes())} nodes)\")\n ray.shutdown()\n return 0\n except (ConnectionError, RuntimeError) as e:\n print(f\"FAIL: {type(e).__name__}: {e}\")\n return 1\n finally:\n os.environ.pop(\"RAY_ADDRESS\", None)\n for p in [pa, pb]:\n if p: stop(p)\n for d in [\"/tmp/ray_a\", \"/tmp/ray_b\"]:\n subprocess.run([\"rm\", \"-rf\", d], check=False)\n\nif __name__ == \"__main__\":\n sys.exit(main())\n", "branch": "bbeb7adbbc8ebaa050dda238a2418e4dd002e80d", "issue_url": "https://github.com/ray-project/ray/issues/60991", "fix_url": "https://github.com/ray-project/ray/pull/61029", "issue_created": "2026-02-11", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ray-61604", "system": "ray", "issue_number": "61604", "lite": false, "title": "[Core] Exception on RuntimeContext.get_node_labels() in local cluster", "description": "What happened + What you expected to happen\nI get this exception with calling RuntimeContext.get_node_labels() in the driver in a local Ray cluster spun up by ray.init():\n\nTraceback (most recent call last):\n File \"/code/labs/jakob/ray/node_labels.py\", line 7, in \n print(ray.runtime_context.get_runtime_context().get_node_labels())\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/local/lib/python3.12/site-packages/ray/runtime_context.py\", line 598, in get_node_labels\n return worker.current_node_labels\n ^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/local/lib/python3.12/site-packages/ray/_private/worker.py\", line 634, in current_node_labels\n return self.node.node_labels\n ^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/local/lib/python3.12/site-packages/ray/_private/node.py\", line 685, in node_labels\n return self._node_labels\n ^^^^^^^^^^^^^^^^^\nAttributeError: 'Node' object has no attribute '_node_labels'. Did you mean: 'node_labels'?\nVersions / Dependencies\nRay 2.54.0\n\nReproduction script\nRun python script.py on a local machine (with RAY_ADDRESS unset), where script.py contains:\n\nimport ray\nray.init()\nprint(ray.runtime_context.get_runtime_context().get_node_labels())\n", "branch": "d334cd6536846bb44d27d6af7b1ddc6106a1e056", "issue_url": "https://github.com/ray-project/ray/issues/61604", "fix_url": "https://github.com/ray-project/ray/pull/61618", "issue_created": "2026-03-09", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ray-61922", "system": "ray", "issue_number": "61922", "lite": false, "title": "[Data] Reference Cycle in ActorMethod.options()", "description": "What happened + What you expected to happen\nThe FuncWrapper class defined inside ActorMethod.options() captures the ActorMethod via a closure cell (func_cls = self). The ActorMethod holds a strong reference to the ActorHandle (self._actor). After .remote() returns, Ray internals keep the FuncWrapper alive, which keeps the ActorMethod alive, which keeps the ActorHandle alive — forming a cycle that CPython's reference counting cannot break.\n\nThis reference cycle has caused delayed garbage collection of ActorHandles and causes problems for Ray Actors to clean up properly with __ray_shutdown__. Details are in the description of this PR.\n\nVersions / Dependencies\nPython\t3.10.19 (conda-forge, Clang 19.1.7)\nOS\tmacOS Darwin 24.6.0 (arm64 / Apple Silicon)\nRay\t3.0.0.dev0 (local dev build)\nPyArrow\t19.0.1\nPandas\t2.3.3\nNumPy\t1.26.4\ngRPC\t1.74.0\naiohttp\t3.13.3\nReproduction script\n\"\"\"Reproduction: reference cycle in ActorMethod.options()\n\nRun:\n python python/ray/data/tests/repro_actor_method_options_ref_cycle.py\n\"\"\"\n\nimport gc\nimport sys\nimport weakref\n\nimport ray\n\n\n@ray.remote\nclass MyActor:\n def __ray_shutdown__(self):\n print(\" >> __ray_shutdown__ called!\")\n\n def task(self, x):\n return x\n\n\ndef trace_chain_from_handle(handle):\n \"\"\"Walk the reference chain: ActorHandle ← ActorMethod ← cell ← FuncWrapper.\"\"\"\n seen = {id(handle)}\n\n # Step 1: Find the ActorMethod holding this handle via ._actor\n actor_method = None\n for ref in gc.get_referrers(handle):\n if type(ref).__name__ == \"frame\" or id(ref) in seen:\n continue\n # ActorMethod stores handle in its __dict__ as '_actor'\n if isinstance(ref, dict) and ref.get(\"_actor\") is handle:\n seen.add(id(ref))\n # Find the object owning this __dict__\n for owner in gc.get_referrers(ref):\n if (\n type(owner).__name__ == \"ActorMethod\"\n and getattr(owner, \"_actor\", None) is handle\n ):\n actor_method = owner\n seen.add(id(owner))\n break\n break\n\n if actor_method is None:\n print(\" ActorHandle ← (no ActorMethod found)\")\n return\n\n method_name = getattr(actor_method, \"_method_name\", \"?\")\n print(f\" ActorHandle\")\n print(f\" ▲\")\n print(f\" └── ActorMethod._actor (method={method_name!r})\")\n\n # Step 2: Find the closure cell holding this ActorMethod\n cell = None\n for ref in gc.get_referrers(actor_method):\n if type(ref).__name__ == \"cell\" and id(ref) not in seen:\n try:\n if ref.cell_contents is actor_method:\n cell = ref\n seen.add(id(ref))\n break\n except ValueError:\n pass\n\n if cell is None:\n print(\" ▲\")\n print(\" └── (no closure cell found)\")\n return\n\n print(\" ▲\")\n print(\" └── closure cell (func_cls = ActorMethod)\")\n\n # Step 3: Find the function whose __closure__ contains this cell\n func = None\n for ref in gc.get_referrers(cell):\n if id(ref) in seen:\n continue\n if isinstance(ref, tuple):\n seen.add(id(ref))\n for owner in gc.get_referrers(ref):\n if callable(owner) and hasattr(owner, \"__closure__\"):\n if owner.__closure__ is ref:\n func = owner\n seen.add(id(owner))\n break\n if func:\n break\n\n if func is None:\n print(\" ▲\")\n print(\" └── (no enclosing function found)\")\n return\n\n qn = getattr(func, \"__qualname__\", repr(func))\n print(\" ▲\")\n print(f\" └── {qn}()\")\n\n # Step 4: Find what holds the function (FuncWrapper instance, etc.)\n for ref in gc.get_referrers(func):\n if id(ref) in seen or type(ref).__name__ == \"frame\":\n continue\n rtype = type(ref).__name__\n if \"FuncWrapper\" in rtype:\n print(\" ▲\")\n print(f\" └── {rtype} instance\")\n elif isinstance(ref, dict):\n # Might be a FuncWrapper's __dict__ or a class __dict__\n for owner in gc.get_referrers(ref):\n otype = type(owner).__name__\n if id(owner) not in seen and otype != \"frame\":\n if \"FuncWrapper\" in otype:\n print(\" ▲\")\n print(f\" └── {otype} instance\")\n elif otype == \"mappingproxy\":\n # Class __dict__ is a mappingproxy\n for cls_ref in gc.get_referrers(owner):\n ctype = type(cls_ref).__name__\n if ctype == \"type\":\n print(\" ▲\")\n print(\n f\" └── class {cls_ref.__name__}\"\n )\n break\n\n\ndef check(weak_handle, label):\n handle = weak_handle()\n if handle is None:\n print(f\" ActorHandle: collected ✓\")\n print()\n return\n print(f\" ActorHandle: ALIVE ✗ (refcount={sys.getrefcount(handle)})\")\n print()\n trace_chain_from_handle(handle)\n print()\n\n\ndef demo_options_remote():\n print(\"=\" * 70)\n print(\"CASE 1: actor.method.options(num_returns=1).remote(42)\")\n print(\" Uses FuncWrapper closure → REFERENCE CYCLE\")\n print(\"=\" * 70)\n\n actor = MyActor.remote()\n weak = weakref.ref(actor)\n\n ref = actor.task.options(num_returns=1).remote(42)\n ray.get(ref)\n\n del actor\n print(\"\\n--- After `del actor` (gc disabled, ref-counting only) ---\")\n print(\" Expecting __ray_shutdown__ to fire... but it does NOT.\")\n check(weak, \"options().remote()\")\n\n del ref\n print(\"--- After also `del ref` (still no gc.collect) ---\")\n print(\" Still no __ray_shutdown__. The cycle keeps the handle alive.\")\n check(weak, \"options().remote()\")\n\n gc.collect()\n print(\"--- After gc.collect() (cyclic GC breaks the cycle) ---\")\n check(weak, \"options().remote()\")\n\n\ndef demo_underscore_remote():\n print(\"=\" * 70)\n print(\"CASE 2: actor.method._remote(args=[42], num_returns=1)\")\n print(\" Direct call, no FuncWrapper → NO CYCLE\")\n print(\"=\" * 70)\n\n actor = MyActor.remote()\n weak = weakref.ref(actor)\n\n ref = actor.task._remote(args=[42], kwargs={}, num_returns=1)\n ray.get(ref)\n\n del actor\n print(\"\\n--- After `del actor` (ref-counting frees it immediately) ---\")\n check(weak, \"_remote()\")\n\n del ref\n print(\"--- After `del ref` ---\")\n check(weak, \"_remote()\")\n\n\nif __name__ == \"__main__\":\n gc.disable()\n ray.init(num_cpus=1)\n print()\n\n demo_options_remote()\n print()\n demo_underscore_remote()\n\n ray.shutdown()\n", "branch": "027d17fbdffc23fb41aaecd24f0c27de93a1293c", "issue_url": "https://github.com/ray-project/ray/issues/61922", "fix_url": "https://github.com/ray-project/ray/pull/61934", "issue_created": "2026-03-20", "severity": "Major", "root_cause_type": "Resource leak", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "ray-62328", "system": "ray", "issue_number": "62328", "lite": false, "title": "[Bug] experimental_mutable_object_manager.cc - Check failed: RAY_PREDICT_TRUE(_left_ != _right_) 0 vs 0", "description": "What happened + What you expected to happen\nHardware\n2x DGX Sparks\n\nSoftware\nSee Reproduction script\n\nError\nThe application starts successfully, when using curl to communicate to the app, the following error appears.\n\n...\n(APIServer pid=1) INFO: Application startup complete.\n(EngineCore pid=107) INFO 04-03 12:10:43 [ray_executor.py:561] RAY_CGRAPH_get_timeout is set to 300\n(EngineCore pid=107) INFO 04-03 12:10:43 [ray_executor.py:565] VLLM_USE_RAY_COMPILED_DAG_CHANNEL_TYPE = nccl\n(EngineCore pid=107) INFO 04-03 12:10:43 [ray_executor.py:569] VLLM_USE_RAY_COMPILED_DAG_OVERLAP_COMM = False\n(EngineCore pid=107) INFO 04-03 12:10:43 [ray_executor.py:634] Using Ray's NCCL communicator for Ray Compiled Graph communication.\n[2026-04-03 12:10:44,576 C 107 107] experimental_mutable_object_manager.cc:177: An unexpected system state has occurred. You have likely discovered a bug in Ray. Please report this issue at https://github.com/ray-project/ray/issues and we'll work with you to fix it. Check failed: RAY_PREDICT_TRUE(_left_ != _right_) 0 vs 0\n*** StackTrace Information ***\n/usr/local/lib/python3.12/dist-packages/ray/_raylet.so(+0x15e60b8) [0xfb07839560b8] ray::operator<<()\n/usr/local/lib/python3.12/dist-packages/ray/_raylet.so(_ZN3ray6RayLogD1Ev+0x5d8) [0xfb0783958b58] ray::RayLog::~RayLog()\n/usr/local/lib/python3.12/dist-packages/ray/_raylet.so(_ZN3ray12experimental20MutableObjectManager14OpenSemaphoresERKNS_8ObjectIDEPNS_18PlasmaObjectHeaderE+0x574) [0xfb0782d7ba54] ray::experimental::MutableObjectManager::OpenSemaphores()\n/usr/local/lib/python3.12/dist-packages/ray/_raylet.so(_ZN3ray12experimental20MutableObjectManager15RegisterChannelERKNS_8ObjectIDESt10unique_ptrIN6plasma13MutableObjectESt14default_deleteIS7_EEb+0xb4) [0xfb0782d7d3f4] ray::experimental::MutableObjectManager::RegisterChannel()\n/usr/local/lib/python3.12/dist-packages/ray/_raylet.so(_ZN3ray4core12experimental21MutableObjectProvider21RegisterReaderChannelERKNS_8ObjectIDE+0x78) [0xfb0782d71a48] ray::core::experimental::MutableObjectProvider::RegisterReaderChannel()\n/usr/local/lib/python3.12/dist-packages/ray/_raylet.so(_ZN3ray4core10CoreWorker39ExperimentalRegisterMutableObjectReaderERKNS_8ObjectIDE+0x20) [0xfb0782d006a0] ray::core::CoreWorker::ExperimentalRegisterMutableObjectReader()\n/usr/local/lib/python3.12/dist-packages/ray/_raylet.so(+0x8d7000) [0xfb0782c47000] __pyx_pw_3ray_7_raylet_10CoreWorker_49experimental_channel_register_reader()\nVLLM::EngineCore(PyObject_Vectorcall+0x4c) [0x4ce52c] PyObject_Vectorcall\nVLLM::EngineCore(_PyEval_EvalFrameDefault+0x67c) [0x4b2fdc] _PyEval_EvalFrameDefault\nVLLM::EngineCore(PyEval_EvalCode+0x84) [0x5a0f44] PyEval_EvalCode\nVLLM::EngineCore() [0x5f0c0c]\nVLLM::EngineCore() [0x5e97e8]\nVLLM::EngineCore(PyRun_StringFlags+0x70) [0x5e3830] PyRun_StringFlags\nVLLM::EngineCore(PyRun_SimpleStringFlags+0x40) [0x5e3530] PyRun_SimpleStringFlags\nVLLM::EngineCore(Py_RunMain+0x404) [0x5df734] Py_RunMain\nVLLM::EngineCore(Py_BytesMain+0x24) [0x5856f4] Py_BytesMain\n/usr/lib/aarch64-linux-gnu/libc.so.6(+0x27400) [0xfb0948527400]\n/usr/lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98) [0xfb09485274d8] __libc_start_main\nVLLM::EngineCore(_start+0x30) [0x585570] _start\n\n(APIServer pid=1) ERROR 04-03 12:10:44 [core_client.py:667] Engine core proc EngineCore died unexpectedly, shutting down client.\n(APIServer pid=1) ERROR 04-03 12:10:44 [async_llm.py:707] AsyncLLM output_handler failed.\n(APIServer pid=1) ERROR 04-03 12:10:44 [async_llm.py:707] Traceback (most recent call last):\n(APIServer pid=1) ERROR 04-03 12:10:44 [async_llm.py:707] File \"/usr/local/lib/python3.12/dist-packages/vllm/v1/engine/async_llm.py\", line 663, in output_handler\n(APIServer pid=1) ERROR 04-03 12:10:44 [async_llm.py:707] outputs = await engine_core.get_output_async()\n(APIServer pid=1) ERROR 04-03 12:10:44 [async_llm.py:707] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n(APIServer pid=1) ERROR 04-03 12:10:44 [async_llm.py:707] File \"/usr/local/lib/python3.12/dist-packages/vllm/v1/engine/core_client.py\", line 985, in get_output_async\n(APIServer pid=1) ERROR 04-03 12:10:44 [async_llm.py:707] raise self._format_exception(outputs) from None\n(APIServer pid=1) ERROR 04-03 12:10:44 [async_llm.py:707] vllm.v1.engine.exceptions.EngineDeadError: EngineCore encountered an issue. See stack trace (above) for the root cause.\n(APIServer pid=1) INFO: 192.168.10.1:56784 - \"POST /v1/chat/completions HTTP/1.1\" 500 Internal Server Error\n(APIServer pid=1) INFO: Shutting down\n(APIServer pid=1) INFO: Waiting for application shutdown.\n(APIServer pid=1) INFO: Application shutdown complete.\n(APIServer pid=1) INFO: Finished server process [1]\nWhat I already tried\nDiffernt types of ENV variables. Also all variations of VLLM_USE_RAY_COMPILED_DAG_CHANNEL_TYPE. Also various docker things, but I think its not related to this issue.\n\nUsed Images:\nvllm/vllm-openai:v0.19.0\nvllm/vllm-openai:v0.18.1\nvllm/vllm-openai:nightly\nnvcr.io/nvidia/vllm:26.03-py3\nnvcr.io/nvidia/vllm:26.02-py3\n\nDisclaimer\nMaybe, I miss something or I am just dumb and dont know how to deactivate the experimental_mutable_object_manager.\n\nVersions / Dependencies\nRay - experimental_mutable_object_manager.cc:177\n\nReproduction script\nSpark1:\n\ndocker run -dit \\\n\t--name ray \\\n\t--gpus all \\\n\t--shm-size=16GB \\\n\t--net=host \\\n\t-e GLOO_SOCKET_IFNAME=enp1s0f0np0 \\\n\t-e NCCL_SOCKET_IFNAME=enp1s0f0np0 \\\n\t-e TP_SOCKET_IFNAME=enp1s0f0np0 \\\n\t-e VLLM_HOST_IP=192.168.10.1 \\\n\t-e VLLM_USE_RAY_WRAPPED_PP_COMM=0 \\\n\t-e RAY_memory_usage_threshold=1.0 \\\n\t-e RAY_memory_monitor_refresh_ms=0 \\\n\t-v ./models/huggingface:/root/.cache/huggingface \\\n\t-v /tmp/ray:/tmp/ray \\\n\t--privileged \\\n\t--entrypoint /bin/bash \\\n\tvllm/vllm-openai:v0.19.0 -c \"pip install ray cupy-cuda12x && ray start --head --block --port=6379 --node-ip-address=192.168.10.1\" \nSpark2:\n\ndocker run -dit --rm \\\n\t--name ray \\\n\t--gpus all \\\n\t--shm-size=16GB \\\n\t--net=host \\\n\t-e GLOO_SOCKET_IFNAME=enp1s0f0np0 \\\n\t-e NCCL_SOCKET_IFNAME=enp1s0f0np0 \\\n\t-e TP_SOCKET_IFNAME=enp1s0f0np0 \\\n\t-e VLLM_HOST_IP=192.168.10.2 \\\n\t-e VLLM_USE_RAY_WRAPPED_PP_COMM=0 \\\n\t-e RAY_memory_usage_threshold=1.0 \\\n\t-e RAY_memory_monitor_refresh_ms=0 \\\n\t-v ./models/huggingface:/root/.cache/huggingface \\\n\t--entrypoint /bin/bash \\\n\t--privileged \\\n\tvllm/vllm-openai:v0.19.0 -c \"pip install ray cupy-cuda12x && ray start --block --node-ip-address=192.168.10.2 --address=192.168.10.1:6379\" \nApplication (Spark1):\n\ndocker run -it --rm \\\n\t--net=host --gpus all \\\n\t-e VLLM_HOST_IP=192.168.10.1 \\\n\t-e VLLM_USE_RAY_WRAPPED_PP_COMM=0 \\\n\t-e VLLM_USE_RAY_COMPILED_DAG_CHANNEL_TYPE=nccl \\\n\t-e VLLM_ENABLE_V1_MULTIPROCESSING=0 \\\n\t-e NCCL_IB_HCA=rocep1s0f0,rocep1s0f1 \\\n\t-e NCCL_IB_GID_INDEX=3 \\\n\t-e NCCL_DEBUG=INFO \\\n\t-e NCCL_SOCKET_IFNAME=enp1s0f0np0 \\\n\t-e GLOO_SOCKET_IFNAME=enp1s0f0np0 \\\n\t-e TP_SOCKET_IFNAME=enp1s0f0np0 \\\n\t-e RAY_ADDRESS=192.168.10.1:6379 \\\n\t-v /tmp/ray:/tmp/ray \\\n\t-v ./../ray/models/huggingface:/root/.cache/huggingface \\\n\t--entrypoint /bin/bash \\\n\tvllm/vllm-openai:v0.19.0 -c \"pip install ray cupy-cuda12x && python3 -m vllm.entrypoints.openai.api_server --model deepseek-ai/DeepSeek-R1-Distill-Llama-70B --distributed-executor-backend ray --tensor-parallel-size 2 --max-model-len 8192 --gpu-memory-utilization 0.8 --trust-remote-code --enforce-eager\"", "branch": "a5ee5309e49895d37b2c2bd964de141df9864fd1", "issue_url": "https://github.com/ray-project/ray/issues/62328", "fix_url": "https://github.com/ray-project/ray/pull/62762", "issue_created": "2026-01-26", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "ray-62430", "system": "ray", "issue_number": "62430", "lite": false, "title": "[Core] idle nodes fail to scale down due to idle_time_ms resetting", "description": "What happened + What you expected to happen\nIdle worker nodes (0 GPU/CPU usage, no scheduled tasks) never scale down while other nodes in the cluster are still running tasks.\nAlso, activity shows up as \"Busy workers on node\" and \"Resource: GPU currently in use\" even when node is idle and idle counter is accumulating.\n\nExpected: each node's idle timer accumulates independently and triggers scale-down after idle_timeout_minutes regardless of peer node activity\n\nActual: idle_duration_ms resets simultaneously on ALL nodes whenever a worker lease is released on ANY node, so the idle timer never accumulates past the inter-task interval\n\nHypothesis: the WorkFootprint/leased-worker tracking introduced to fix \"blocked task\" misclassification appears to reset idle_duration_ms cluster-wide as a side effect of worker lease lifecycle events. The autoscaler.py scale-down decision is correctly per-node, but the idle_duration_ms signal from GetClusterResourceState is being corrupted by unrelated nodes' lease events\n\nVersions / Dependencies\nRay version: 2.54.0\nOS: Linux (GCP)\nPython version: Python 3.10.12\nGPU: 4x nodes × 2x V100\nAutoscaler: v2", "branch": "e4d0c470b5f97d461a19f6321dcaba97ec69aeab", "issue_url": "https://github.com/ray-project/ray/issues/62430", "fix_url": "https://github.com/ray-project/ray/pull/62588", "issue_created": "2026-04-08", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "tikv-16818", "system": "tikv", "issue_number": "16818", "lite": false, "title": "tikv panic for \"assertion failed: row.lock.is_none()\"", "description": "Bug Report\nWhat version of TiKV are you using?\n\n[\"Git Commit Hash: b7103fa\"] [thread_id=1]\nWhat operating system and CPU are you using?\nSteps to reproduce\n\nbank-tbls-pessimistic-inplace-follower-neterr\ntxn-mode=pessimistic, follower-read=true\nrun bank workload,\ninjuct network fail\nparams:\n--txn-mode=pessimistic --force-reinstall=true --update-in-place=true\n--follower-read=true\n--nemesis=schedules,partition-pd-leader,partition-half,partition-ring\n--read-lock=update --os=image --time-limit=600 --version=master\n--workload=bank-multitable --init-sql='set\n@@tidb_enable_mutation_checker=1, @@tidb_txn_assertion_level=strict,\n@@tidb_constraint_check_in_place_pessimistic=off'\nWhat did you expect?\n\npass\nWhat did happened?\n\n[2024/04/11 19:01:19.274 +00:00] [FATAL] [lib.rs:477] [\"assertion failed: row.lock.is_none()\"] [backtrace=\" 0: tikv_util::set_panic_hook::{{closure}}\n at /workspace/source/tikv/components/tikv_util/src/lib.rs:476:18\n 1: as core::ops::function::Fn>::call\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2029:9\n std::panicking::rust_panic_with_hook\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:783:13\n 2: std::panicking::begin_panic_handler::{{closure}}\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:649:13\n 3: std::sys_common::backtrace::__rust_end_short_backtrace\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:171:18\n 4: rust_begin_unwind\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:645:5\n 5: core::panicking::panic_fmt\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:72:14\n 6: core::panicking::panic\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:144:5\n 7: resolved_ts::cmd::group_row_changes\n at /workspace/source/tikv/components/resolved_ts/src/cmd.rs:224:25\n resolved_ts::cmd::ChangeLog::encode_change_log::{{closure}}\n at /workspace/source/tikv/components/resolved_ts/src/cmd.rs:62:57\n core::iter::adapters::map::map_fold::{{closure}}\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/iter/adapters/map.rs:85:28\n core::iter::traits::iterator::Iterator::fold\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/iter/traits/iterator.rs:2640:21\n as core::iter::traits::iterator::Iterator>::fold\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/iter/adapters/map.rs:125:9\n core::iter::traits::iterator::Iterator::for_each\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/iter/traits/iterator.rs:858:9\n alloc::vec::Vec::extend_trusted\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/mod.rs:2923:17\n as alloc::vec::spec_extend::SpecExtend>::spec_extend\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/spec_extend.rs:26:9\n as alloc::vec::spec_from_iter_nested::SpecFromIterNested>::from_iter\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/spec_from_iter_nested.rs:62:9\n alloc::vec::in_place_collect:: for alloc::vec::Vec>::from_iter\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/in_place_collect.rs:233:20\n as core::iter::traits::collect::FromIterator>::from_iter\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/mod.rs:2791:9\n core::iter::traits::iterator::Iterator::collect\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/iter/traits/iterator.rs:2054:9\n resolved_ts::cmd::ChangeLog::encode_change_log\n at /workspace/source/tikv/components/resolved_ts/src/cmd.rs:76:14\n 8: resolved_ts::endpoint::Endpoint::handle_change_log\n at /workspace/source/tikv/components/resolved_ts/src/endpoint.rs:883:32\n as tikv_util::worker::pool::Runnable>::run\n at /workspace/source/tikv/components/resolved_ts/src/endpoint.rs:1132:46\n tikv_util::worker::pool::Worker::start_with_timer_impl::{{closure}}\n at /workspace/source/tikv/components/tikv_util/src/worker/pool.rs:517:25\n 9: as core::future::future::Future>::poll::{{closure}}\n at /workspace/source/tikv/components/tracker/src/tls.rs:64:23\n std::thread::local::LocalKey::try_with\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:270:16\n std::thread::local::LocalKey::with\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:246:9\n as core::future::future::Future>::poll\n at /workspace/source/tikv/components/tracker/src/tls.rs:62:27\n as core::future::future::Future>::poll\n at /workspace/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.15/src/future/future/map.rs:55:37\n as core::future::future::Future>::poll\n at /workspace/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.15/src/lib.rs:93:13\n yatp::task::future::RawTask::poll\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/task/future.rs:59:9\n 10: yatp::task::future::TaskCell::poll\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/task/future.rs:103:9\n ::handle\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/task/future.rs:387:20\n 11: as yatp::pool::runner::Runner>::handle\n at /workspace/source/tikv/components/tikv_util/src/yatp_pool/mod.rs:198:24\n yatp::pool::worker::WorkerThread::run\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/pool/worker.rs:48:13\n yatp::pool::builder::LazyBuilder::build::{{closure}}\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/pool/builder.rs:114:25\n std::sys_common::backtrace::__rust_begin_short_backtrace\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:155:18\n 12: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:529:17\n as core::ops::function::FnOnce<()>>::call_once\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:272:9\n std::panicking::try::do_call\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:552:40\n std::panicking::try\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:516:19\n std::panic::catch_unwind\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:142:14\n std::thread::Builder::spawn_unchecked_::{{closure}}\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:528:30\n core::ops::function::FnOnce::call_once{{vtable.shim}}\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5\n 13: as core::ops::function::FnOnce>::call_once\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2015:9\n as core::ops::function::FnOnce>::call_once\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2015:9\n std::sys::unix::thread::Thread::new::thread_start\n at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/unix/thread.rs:108:17\n 14: start_thread\n 15: clone\n\"] [location=components/resolved_ts/src/cmd.rs:224] [thread_name=resolved-ts-0] [thread_id=75]\n\n", "branch": "2f3f32d9a0de2ebdb987c00b2419761cfbda4556", "issue_url": "https://github.com/tikv/tikv/issues/16818", "fix_url": "https://github.com/tikv/tikv/pull/18115", "issue_created": "2024-04-12", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "tikv-17830", "system": "tikv", "issue_number": "17830", "lite": false, "title": "tikv panics when injecting pd failure during add multi index", "description": "Bug Report\nWhat version of TiKV are you using?\n\nv7.1.6\nWhat operating system and CPU are you using?\nSteps to reproduce\n\nIn the process of adding multi index, inject pd failure fault\nWhat did you expect?\n\nno tikv panic\nWhat did happened?\n\n{\"log\":\"[lib.rs:510] [\"Resolved future is not supposed to be polled again.\"] [backtrace=\" 0: tikv_util::set_panic_hook::{{closure}}\\n at workspace/source/tikv/components/tikv_util/src/lib.rs:509:18\\n 1: as core::ops::function::Fn>::call\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2032:9\\n std::panicking::rust_panic_with_hook\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:692:13\\n 2: std::panicking::begin_panic::{{closure}}\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:608:9\\n 3: std::sys_common::backtrace::__rust_end_short_backtrace\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:137:18\\n 4: std::panicking::begin_panic\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:607:12\\n 5: ::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/grpcio-0.10.4/src/task/mod.rs:90:13\\n 6: grpcio::call::SinkBase::poll_ready\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/grpcio-0.10.4/src/call/mod.rs:796:24\\n 7: >::poll_close\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/grpcio-0.10.4/src/call/server.rs:562:28\\n <&mut S as futures_sink::Sink>::poll_close\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/futures-sink-0.3.15/src/lib.rs:130:9\\n as core::future::future::Future>::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/futures-util-0.3.15/src/sink/close.rs:30:9\\n 8: ::duplicate_detect::{{closure}}\\n at workspace/source/tikv/src/import/sst_service.rs:1300:33\\n ::poll\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\\n tokio::runtime::task::core::CoreStage::poll::{{closure}}\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/core.rs:184:17\\n tokio::loom::std::unsafe_cell::UnsafeCell::with_mut\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/loom/std/unsafe_cell.rs:14:9\\n tokio::runtime::task::core::CoreStage::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/core.rs:174:13\\n 9: tokio::runtime::task::harness::poll_future::{{closure}}\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/harness.rs:480:19\\n >::call_once\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:271:9\\n std::panicking::try::do_call\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:483:40\\n std::panicking::try\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:447:19\\n std::panic::catch_unwind\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:137:14\\n tokio::runtime::task::harness::poll_future\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/harness.rs:468:18\\n tokio::runtime::task::harness::Harness::poll_inner\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/harness.rs:104:27\\n tokio::runtime::task::harness::Harness::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/harness.rs:57:15\\n tokio::runtime::task::raw::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/raw.rs:194:5\\n 10: tokio::runtime::task::raw::RawTask::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/raw.rs:134:18\\n tokio::runtime::task::LocalNotified::run\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/mod.rs:385:9\\n tokio::runtime::scheduler::multi_thread::worker::Context::run_task::{{closure}}\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/scheduler/multi_thread/worker.rs:421:13\\n tokio::coop::with_budget::{{closure}}\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/coop.rs:102:9\\n std::thread::local::LocalKey::try_with\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:446:16\\n std::thread::local::LocalKey::with\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:422:9\\n tokio::coop::with_budget\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/coop.rs:95:5\\n tokio::coop::budget\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/coop.rs:72:5\\n tokio::runtime::scheduler::multi_thread::worker::Context::run_task\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/scheduler/multi_thread/worker.rs:420:9\\n 11: tokio::runtime::scheduler::multi_thread::worker::Context::run\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/scheduler/multi_thread/worker.rs:387:24\\n tokio::runtime::scheduler::multi_thread::worker::run::{{closure}}\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/scheduler/multi_thread/worker.rs:372:17\\n tokio::macros::scoped_tls::ScopedKey::set\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/macros/scoped_tls.rs:61:9\\n tokio::runtime::scheduler::multi_thread::worker::run\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/scheduler/multi_thread/worker.rs:369:5\\n tokio::runtime::scheduler::multi_thread::worker::Launch::launch::{{closure}}\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/scheduler/multi_thread/worker.rs:348:45\\n ::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/blocking/task.rs:42:21\\n tokio::runtime::task::core::CoreStage::poll::{{closure}}\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/core.rs:184:17\\n tokio::loom::std::unsafe_cell::UnsafeCell::with_mut\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/loom/std/unsafe_cell.rs:14:9\\n tokio::runtime::task::core::CoreStage::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/core.rs:174:13\\n tokio::runtime::task::harness::poll_future::{{closure}}\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/harness.rs:480:19\\n >::call_once\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:271:9\\n std::panicking::try::do_call\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:483:40\\n std::panicking::try\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:447:19\\n std::panic::catch_unwind\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:137:14\\n tokio::runtime::task::harness::poll_future\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/harness.rs:468:18\\n tokio::runtime::task::harness::Harness::poll_inner\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/harness.rs:104:27\\n tokio::runtime::task::harness::Harness::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/harness.rs:57:15\\n tokio::runtime::task::raw::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/raw.rs:194:5\\n 12: tokio::runtime::task::raw::RawTask::poll\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/raw.rs:134:18\\n tokio::runtime::task::UnownedTask::run\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/task/mod.rs:422:9\\n tokio::runtime::blocking::pool::Task::run\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/blocking/pool.rs:111:9\\n tokio::runtime::blocking::pool::Inner::run\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/blocking/pool.rs:346:17\\n tokio::runtime::blocking::pool::Spawner::spawn_thread::{{closure}}\\n at workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/tokio-1.21.2/src/runtime/blocking/pool.rs:321:13\\n std::sys_common::backtrace::rust_begin_short_backtrace\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:121:18\\n 13: std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}}\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:551:17\\n >::call_once\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:271:9\\n std::panicking::try::do_call\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:483:40\\n std::panicking::try\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:447:19\\n std::panic::catch_unwind\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:137:14\\n std::thread::Builder::spawn_unchecked::{{closure}}\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:550:30\\n core::ops::function::FnOnce::call_once{{vtable.shim}}\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:513:5\\n 14: as core::ops::function::FnOnce>::call_once\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2000:9\\n as core::ops::function::FnOnce>::call_once\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2000:9\\n std::sys::unix::thread::Thread::new::thread_start\\n at root/.rustup/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/unix/thread.rs:108:17\\n 15: start_thread\\n 16: clone3\\n\"] [location=/workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/grpcio-0.10.4/src/task/mod.rs:90] [thread_name=sst-importer]\",\"container\":\"tikv\",\"pod\":\"tc-tikv-0\",\"level\":\"FATAL\",\"namespace\":\"endless-ha-test-tps-7682088-1-507\"}", "branch": "v7.1.6", "issue_url": "https://github.com/tikv/tikv/issues/17830", "fix_url": "https://github.com/tikv/tikv/pull/17834", "issue_created": "2024-11-15", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "tikv-18317", "system": "tikv", "issue_number": "18317", "lite": false, "title": "There is a 15.4% performance regression in ycsb after PR#18248", "description": "Bug Report\nWhat version of TiKV are you using?\n\n71aecc2\nWhat operating system and CPU are you using?\n\nK8S, x86\nSteps to reproduce\n\n Deploy a cluster with 3 TiDB and 3 Tikv.\n Run benchmark ycsb (workloada).\n\nWhat did you expect?\n\nNo performance regression.\nWhat did happened?\n\nDuration regression in benchmark ycsb (workloada) compared to baseline 169.00 after #18248.\ndescription \ttidb \ttikv \tpd \tDuration\nlast success \tpingcap/tidb@db15d43 \t3035868 \ttikv/pd@a695261 \t168.00, 162.00\nfirst regression \tpingcap/tidb@db15d43 \t71aecc2 \ttikv/pd@a695261 \t195.00, 190.00", "branch": "71aecc2", "issue_url": "https://github.com/tikv/tikv/issues/18317", "fix_url": "https://github.com/tikv/tikv/pull/18321", "issue_created": "2025-03-18", "severity": "Major", "root_cause_type": "Performance", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "tikv-18458", "system": "tikv", "issue_number": "18458", "lite": true, "title": "unsafe recovery: some tables are always unavailable when alter tiflash replica after unsafe recovery finished with tiflash", "description": "Bug Report\nWhat version of TiKV are you using?\nTiKV\nRelease Version: 8.5.2\nEdition: Community\nGit Commit Hash: a150e45\nGit Commit Branch: HEAD\nUTC Build Time: 2025-04-24 12:10:31\nRust Version: rustc 1.77.0-nightly (89e2160c4 2023-12-27)\nEnable Features: memory-engine pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine trace-async-tasks openssl-vendored\nProfile: dist_release\n\nWhat operating system and CPU are you using?\n8c/16g\n\nSteps to reproduce\n1、dr auto sync deploy with tiflash 2 replicas\n2、run tpcc\n3、unsafe remove-failed-stores (include one tiflash) succeed\n\"region 52973 demotes peers { id:52974 store_id:1 }, { id:52976 store_id:9 }, { id:52979 store_id:2 }, { id:52980 store_id:502 role:Learner }\", \"region 52927 demotes peers { id:52928 store_id:1 }, { id:52930 store_id:9 }, { id:52933 store_id:2 }\", \"region 52982 demotes peers { id:52983 store_id:1 }, { id:52985 store_id:9 }, { id:52988 store_id:2 }\", \"region 52989 demotes peers { id:52990 store_id:1 }, { id:52992 store_id:9 }, { id:52995 store_id:2 }\", \"region 52996 demotes peers { id:52997 store_id:1 }, { id:52999 store_id:9 }, { id:53002 store_id:2 }\", \"region 53003 demotes peers { id:53004 store_id:1 }, { id:53006 store_id:9 }, { id:53009 store_id:2 }\", \"region 53061 demotes peers { id:53062 store_id:1 }, { id:53064 store_id:9 }, { id:53067 store_id:2 }\", \"region 53038 demotes peers { id:53039 store_id:1 }, { id:53041 store_id:9 }, { id:53044 store_id:2 }\", \"region 53068 demotes peers { id:53069 store_id:1 }, { id:53071 store_id:9 }, { id:53074 store_id:2 }\", \"region 53010 demotes peers { id:53011 store_id:1 }, { id:53013 store_id:9 }, { id:53016 store_id:2 }\", \"region 53017 demotes peers { id:53018 store_id:1 }, { id:53020 store_id:9 }, { id:53023 store_id:2 }\", \"region 53024 demotes peers { id:53025 store_id:1 }, { id:53027 store_id:9 }, { id:53030 store_id:2 }\", \"region 53031 demotes peers { id:53032 store_id:1 }, { id:53034 store_id:9 }, { id:53037 store_id:2 }\", \"region 16 demotes peers { id:17 store_id:1 }, { id:28 store_id:9 }, { id:37 store_id:2 }\", \"region 18 demotes peers { id:19 store_id:1 }, { id:27 store_id:2 }, { id:499 store_id:9 }\", \"region 3 demotes peers { id:29 store_id:9 }, { id:39 store_id:2 }, { id:472 store_id:1 }\" ], \"store 8\": [ \"region 567 demotes peers { id:568 store_id:1 }, { id:570 store_id:9 }, { id:573 store_id:2 }\", \"region 2100 demotes peers { id:2101 store_id:1 }, { id:2103 store_id:9 }, { id:2106 store_id:2 }\", \"region 53045 demotes peers { id:53046 store_id:1 }, { id:53048 store_id:9 }, { id:53051 store_id:2 }\", \"region 83 demotes peers { id:84 store_id:1 }, { id:86 store_id:9 }, { id:468 store_id:2 }\" ] } }, { \"info\": \"Unsafe recovery Finished\", \"time\": \"2025-05-06 12:45:01.366\", \"details\": [ \"affected table ids: 157, 158, 129, 156, 120, 127, 168, 174, 281474976710648, 124, 155, 176, 178, 172, 126, 125, 152, 170, 122, 123, 180, 121, 28, 153, 154, 26, 108, 128, 182\", \"no newly created empty regions\" ] } ]\n\nWhat did you expect?\nsome tables are always unavailable after alter tiflash replica\n\nWhat did happened?\nsome tables are always unavailable after alter tiflash replica\n\nImage", "branch": "a150e45", "issue_url": "https://github.com/tikv/tikv/issues/18458", "fix_url": "https://github.com/tikv/tikv/pull/18760", "issue_created": "2025-05-21", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "tikv-18498", "system": "tikv", "issue_number": "18498", "lite": true, "title": "cdc: fixing a TiKV assertion panic that can happen when CDC is enabled", "description": "Bug Report\nWhat version of TiKV are you using?\nv8.5.1\n\nWhat operating system and CPU are you using?\nSteps to reproduce\nWhat did you expect?\nWhat did happened?\n{\"level\":\"INFO\",\"caller\":\"raft.rs:2684\",\"message\":\"switched to configuration\",\"time\":\"2025/05/29 02:44:22.563 +00:00\",\"raft_id\":12700241,\"region_id\":12700240,\"thread_id\":156,\"config\":\"Configuration { voters: Configuration { incoming: Configuration { voters: {24087147, 12700242, 12700241} }, outgoing: Configuration { voters: {} } }, learners: {}, learners_next: {}, auto_leave: false }\"}\n{\"level\":\"FATAL\",\"caller\":\"lib.rs:479\",\"message\":\"assertion `left == right` failed\\n left: TimeStamp(458355287523328275)\\n right: TimeStamp(458355287523328316)\",\"time\":\"2025/05/29 02:44:22.737 +00:00\",\"thread_id\":47,\"backtrace\":\" 0: tikv_util::set_panic_hook::{{closure}}\\n at /workspace/source/tikv/components/tikv_util/src/lib.rs:478:18\\n 1: as core::ops::function::Fn>::call\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2029:9\\n std::panicking::rust_panic_with_hook\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:783:13\\n 2: std::panicking::begin_panic_handler::{{closure}}\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:657:13\\n 3: std::sys_common::backtrace::__rust_end_short_backtrace\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:171:18\\n 4: rust_begin_unwind\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:645:5\\n 5: core::panicking::panic_fmt\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:72:14\\n 6: core::panicking::assert_failed_inner\\n 7: core::panicking::assert_failed\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:297:5\\n 8: cdc::delegate::Delegate::push_lock\\n at /workspace/source/tikv/components/cdc/src/delegate.rs:374:21\\n cdc::delegate::Delegate::sink_txn_put\\n at /workspace/source/tikv/components/cdc/src/delegate.rs:1054:41\\n cdc::delegate::Delegate::sink_put\\n at /workspace/source/tikv/components/cdc/src/delegate.rs:1003:13\\n cdc::delegate::Delegate::sink_data\\n at /workspace/source/tikv/components/cdc/src/delegate.rs:871:33\\n 9: cdc::delegate::Delegate::on_batch\\n at /workspace/source/tikv/components/cdc/src/delegate.rs:734:17\\n 10: cdc::endpoint::Endpoint::on_multi_batch\\n at /workspace/source/tikv/components/cdc/src/endpoint.rs:999:33\\n as tikv_util::worker::pool::Runnable>::run\\n at /workspace/source/tikv/components/cdc/src/endpoint.rs:1225:18\\n 11: tikv_util::worker::pool::Worker::start_with_timer_impl::{{closure}}\\n at /workspace/source/tikv/components/tikv_util/src/worker/pool.rs:532:25\\n as core::future::future::Future>::poll::{{closure}}\\n at /workspace/source/tikv/components/tracker/src/tls.rs:64:23\\n std::thread::local::LocalKey::try_with\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:270:16\\n std::thread::local::LocalKey::with\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:246:9\\n as core::future::future::Future>::poll\\n at /workspace/source/tikv/components/tracker/src/tls.rs:62:27\\n as core::future::future::Future>::poll\\n at /workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/futures-util-0.3.31/src/future/future/map.rs:55:37\\n as core::future::future::Future>::poll\\n at /workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/futures-util-0.3.31/src/lib.rs:86:13\\n yatp::task::future::RawTask::poll\\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/task/future.rs:59:9\\n 12: yatp::task::future::TaskCell::poll\\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/task/future.rs:103:9\\n ::handle\\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/task/future.rs:387:20\\n 13: as yatp::pool::runner::Runner>::handle\\n at /workspace/source/tikv/components/tikv_util/src/yatp_pool/mod.rs:199:24\\n yatp::pool::worker::WorkerThread::run\\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/pool/worker.rs:48:13\\n yatp::pool::builder::LazyBuilder::build::{{closure}}\\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/pool/builder.rs:114:25\\n std::sys_common::backtrace::__rust_begin_short_backtrace\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:155:18\\n 14: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:529:17\\n as core::ops::function::FnOnce<()>>::call_once\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:272:9\\n std::panicking::try::do_call\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:552:40\\n std::panicking::try\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:516:19\\n std::panic::catch_unwind\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:142:14\\n std::thread::Builder::spawn_unchecked_::{{closure}}\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:528:30\\n core::ops::function::FnOnce::call_once{{vtable.shim}}\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5\\n 15: as core::ops::function::FnOnce>::call_once\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2015:9\\n as core::ops::function::FnOnce>::call_once\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2015:9\\n std::sys::unix::thread::Thread::new::thread_start\\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/unix/thread.rs:108:17\\n 16: start_thread\\n 17: thread_start\\n\",\"location\":\"components/cdc/src/delegate.rs:374\",\"thread_name\":\"cdc-0\"}\n{\"level\":\"INFO\",\"caller\":\"lib.rs:91\",\"message\":\"Welcome to TiKV\",\"time\":\"2025/05/29 02:44:42.869 +00:00\",\"thread_id\":1}\n{\"level\":\"INFO\",\"caller\":\"lib.rs:96\",\"message\":\"Release Version: 8.5.1\",\"time\":\"2025/05/29 02:44:42.870 +00:00\",\"thread_id\":1}\n{\"level\":\"INFO\",\"caller\":\"lib.rs:96\",\"message\":\"Edition: Enterprise\",\"time\":\"2025/05/29 02:44:42.870 +00:00\",\"thread_id\":1}\n{\"level\":\"INFO\",\"caller\":\"lib.rs:96\",\"message\":\"Git Commit Hash: 25897b73e1f0e93f616c764dbe65ed7db02edd07\",\"time\":\"2025/05/29 02:44:42.870 +00:00\",\"thread_id\":1}\n 0: tikv_util::set_panic_hook::{{closure}}\n at /workspace/source/tikv/components/tikv_util/src/lib.rs:478:18\n 1: as core::ops::function::Fn>::call\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2029:9\n std::panicking::rust_panic_with_hook\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:783:13\n 2: std::panicking::begin_panic_handler::{{closure}}\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:657:13\n 3: std::sys_common::backtrace::__rust_end_short_backtrace\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:171:18\n 4: rust_begin_unwind\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:645:5\n 5: core::panicking::panic_fmt\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:72:14\n 6: core::panicking::assert_failed_inner\n 7: core::panicking::assert_failed\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:297:5\n 8: cdc::delegate::Delegate::push_lock\n at /workspace/source/tikv/components/cdc/src/delegate.rs:374:21\n cdc::delegate::Delegate::sink_txn_put\n at /workspace/source/tikv/components/cdc/src/delegate.rs:1054:41\n cdc::delegate::Delegate::sink_put\n at /workspace/source/tikv/components/cdc/src/delegate.rs:1003:13\n cdc::delegate::Delegate::sink_data\n at /workspace/source/tikv/components/cdc/src/delegate.rs:871:33\n 9: cdc::delegate::Delegate::on_batch\n at /workspace/source/tikv/components/cdc/src/delegate.rs:734:17\n 10: cdc::endpoint::Endpoint::on_multi_batch\n at /workspace/source/tikv/components/cdc/src/endpoint.rs:999:33\n as tikv_util::worker::pool::Runnable>::run\n at /workspace/source/tikv/components/cdc/src/endpoint.rs:1225:18\n 11: tikv_util::worker::pool::Worker::start_with_timer_impl::{{closure}}\n at /workspace/source/tikv/components/tikv_util/src/worker/pool.rs:532:25\n as core::future::future::Future>::poll::{{closure}}\n at /workspace/source/tikv/components/tracker/src/tls.rs:64:23\n std::thread::local::LocalKey::try_with\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:270:16\n std::thread::local::LocalKey::with\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:246:9\n as core::future::future::Future>::poll\n at /workspace/source/tikv/components/tracker/src/tls.rs:62:27\n as core::future::future::Future>::poll\n at /workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/futures-util-0.3.31/src/future/future/map.rs:55:37\n as core::future::future::Future>::poll\n at /workspace/.cargo/registry/src/mirrors.tuna.tsinghua.edu.cn-df7c3c540f42cdbd/futures-util-0.3.31/src/lib.rs:86:13\n yatp::task::future::RawTask::poll\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/task/future.rs:59:9\n 12: yatp::task::future::TaskCell::poll\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/task/future.rs:103:9\n ::handle\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/task/future.rs:387:20\n 13: as yatp::pool::runner::Runner>::handle\n at /workspace/source/tikv/components/tikv_util/src/yatp_pool/mod.rs:199:24\n yatp::pool::worker::WorkerThread::run\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/pool/worker.rs:48:13\n yatp::pool::builder::LazyBuilder::build::{{closure}}\n at /workspace/.cargo/git/checkouts/yatp-e704b73c3ee279b6/793be4d/src/pool/builder.rs:114:25\n std::sys_common::backtrace::__rust_begin_short_backtrace\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:155:18\n 14: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:529:17\n as core::ops::function::FnOnce<()>>::call_once\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:272:9\n std::panicking::try::do_call\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:552:40\n std::panicking::try\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:516:19\n std::panic::catch_unwind\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:142:14\n std::thread::Builder::spawn_unchecked_::{{closure}}\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:528:30\n core::ops::function::FnOnce::call_once{{vtable.shim}}\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5\n 15: as core::ops::function::FnOnce>::call_once\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2015:9\n as core::ops::function::FnOnce>::call_once\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2015:9\n std::sys::unix::thread::Thread::new::thread_start\n at /root/.rustup/toolchains/nightly-2023-12-28-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/unix/thread.rs:108:17\n 16: start_thread\n 17: thread_start", "branch": "v8.5.1", "issue_url": "https://github.com/tikv/tikv/issues/18498", "fix_url": "https://github.com/tikv/tikv/pull/19025", "issue_created": "2025-06-03", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "tikv-18756", "system": "tikv", "issue_number": "18756", "lite": false, "title": "tikv random memory fault in test_compaction_filter_blocked_by_clean_overlap_", "description": "Bug Report\nA low-probablity random failure:\n\n(lldb) bt\n* thread #113, name = 'region-worker::test_compaction_filter_blocked_by_clean_overlap_', stop reason = EXC_BAD_ACCESS (code=1, address=0xd)\n * frame #0: 0x00000001878058b0 libsystem_pthread.dylib`pthread_mutex_unlock + 12\n frame #1: 0x00000001051e145c failpoints-82c0c2b744de936d`_$LT$std..sync..poison..mutex..MutexGuard$LT$T$GT$$u20$as$u20$core..ops..drop..Drop$GT$::drop::h57c50fdae54a6bf6 + 56\n frame #2: 0x00000001051ab06c failpoints-82c0c2b744de936d`core::ptr::drop_in_place$LT$std..sync..poison..mutex..MutexGuard$LT$$LP$$RP$$GT$$GT$::hd863acc306193875 + 12\n frame #3: 0x00000001049e4098 failpoints-82c0c2b744de936d`core::ptr::drop_in_place$LT$tikv_util..range_latch..RangeLatchGuard$GT$::h89f35907d4c0e6cc + 108\n frame #4: 0x00000001049e4cfc failpoints-82c0c2b744de936d`core::ptr::drop_in_place$LT$core..option..Option$LT$tikv_util..range_latch..RangeLatchGuard$GT$$GT$::hac15ba0060781a6e + 60\n frame #5: 0x0000000104a0a96c failpoints-82c0c2b744de936d`engine_rocks::import::_$LT$impl$u20$engine_traits..import..ImportExt$u20$for$u20$engine_rocks..engine..RocksEngine$GT$::ingest_external_file_cf::h6a04738e2235dadf + 1092\n frame #6: 0x0000000104a0aee4 failpoints-82c0c2b744de936d`engine_rocks::misc::_$LT$impl$u20$engine_rocks..engine..RocksEngine$GT$::delete_all_in_range_cf_by_ingest::h5c8d3c1b5a66a4cb + 1140\n frame #7: 0x0000000104a0d0a4 failpoints-82c0c2b744de936d`engine_rocks::misc::_$LT$impl$u20$engine_traits..misc..MiscExt$u20$for$u20$engine_rocks..engine..RocksEngine$GT$::delete_ranges_cf::h39764cfc68ef1810 + 488\nWhat version of TiKV are you using?\nv9.0.x\n\nWhat operating system and CPU are you using?\nMacOS\n\nSteps to reproduce\nTry running tests many times\n\nWhat did you expect?\nTest passes.\n\nWhat did happened?\nTest failure with memory fault", "branch": "ed504baa35c36fa2f05ee1e5bb8f5e3f60da46d6", "issue_url": "https://github.com/tikv/tikv/issues/18756", "fix_url": "https://github.com/tikv/tikv/pull/18765", "issue_created": "2025-07-29", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "tikv-18912", "system": "tikv", "issue_number": "18912", "lite": false, "title": "tikv panic during adding index or lighting import", "description": "Bug Report\nWhat version of TiKV are you using?\n./tikv-server -V\nTiKV\nRelease Version: 9.0.0-beta.2\nEdition: Community\nGit Commit Hash: 2d51d3e\nGit Commit Branch: HEAD\nUTC Build Time: 2025-08-29 03:24:59\nRust Version: rustc 1.87.0-nightly (96cfc7558 2025-02-27)\nEnable Features: memory-engine pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine trace-async-tasks openssl-vendored\nProfile: dist_release\n2025-09-01T01:10:11.258+0800 INFO k8s/client.go:141 it should be noted that a long-running command will not be interrupted even the use case has ended. For more information, please refer to https://github.com/pingcap/test-infra/discussions/129\n\nWhat operating system and CPU are you using?\n8c32g\n\nSteps to reproduce\n1、run sysbench\n2、adding index for one table with global sort\n\nWhat did you expect?\nno panic\n\nWhat did happened?\ntikv panic during adding index\n2025-09-01 09:08:39.131\n{\"log\":\"[lib.rs:549] [\"assertion failed: last_key < next_key\"] [backtrace=\" 0: tikv_util::set_panic_hook::{{closure}}\\n at workspace/source/tikv/components/tikv_util/src/lib.rs:546:18\\n 1: as core::ops::function::Fn>::call\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1986:9\\n std::panicking::rust_panic_with_hook\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:839:13\\n 2: std::panicking::begin_panic_handler::{{closure}}\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:697:13\\n 3: std::sys::backtrace::__rust_end_short_backtrace\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/backtrace.rs:168:18\\n 4: rust_begin_unwind\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:695:5\\n 5: core::panicking::panic_fmt\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:75:14\\n 6: core::panicking::panic\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:145:5\\n 7: raftstore::store::compaction_guard::overlap_with\\n at workspace/source/tikv/components/raftstore/src/store/compaction_guard.rs:332:5\\n 8: ::can_do_trivial_move\\n at workspace/source/tikv/components/raftstore/src/store/compaction_guard.rs:435:10\\n ::can_do_trivial_move\\n at workspace/source/tikv/components/engine_rocks/src/sst_partitioner.rs:56:9\\n rocksdb::sst_partitioner::sst_partitioner_can_do_trivial_move\\n at workspace/.cargo/git/checkouts/rust-rocksdb-882d3d9019f8b391/1fa430f/src/sst_partitioner.rs:79:5\\n 9: ZN31crocksdb_sst_partitioner_impl_t16CanDoTrivialMoveERKN7rocksdb5SliceES3\\n at workspace/.cargo/git/checkouts/rust-rocksdb-882d3d9019f8b391/1fa430f/librocksdb_sys/crocksdb/c.cc:6476:34\\n 10: _ZNK7rocksdb10Compaction13IsTrivialMoveEv\\n at workspace/.cargo/git/checkouts/rust-rocksdb-882d3d9019f8b391/1fa430f/librocksdb_sys/rocksdb/db/compaction/compaction.cc:584:43\\n 11: _ZN7rocksdb6DBImpl20BackgroundCompactionEPbPNS_10JobContextEPNS_9LogBufferEPNS0_19PrepickedCompactionENS_3Env8PriorityE\\n at workspace/.cargo/git/checkouts/rust-rocksdb-882d3d9019f8b391/1fa430f/librocksdb_sys/rocksdb/db/db_impl/db_impl_compaction_flush.cc:3746:58\\n 12: _ZN7rocksdb6DBImpl24BackgroundCallCompactionEPNS0_19PrepickedCompactionENS_3Env8PriorityE\\n at workspace/.cargo/git/checkouts/rust-rocksdb-882d3d9019f8b391/1fa430f/librocksdb_sys/rocksdb/db/db_impl/db_impl_compaction_flush.cc:3398:72\\n 13: _ZN7rocksdb6DBImpl16BGWorkCompactionEPv\\n at workspace/.cargo/git/checkouts/rust-rocksdb-882d3d9019f8b391/1fa430f/librocksdb_sys/rocksdb/db/db_impl/db_impl_compaction_flush.cc:3070:66\\n 14: _ZNKSt8functionIFvvEEclEv\\n at opt/rh/devtoolset-8/root/usr/include/c++/8/bits/std_function.h:687:14\\n _ZN7rocksdb14ThreadPoolImpl4Impl8BGThreadEm\\n at workspace/.cargo/git/checkouts/rust-rocksdb-882d3d9019f8b391/1fa430f/librocksdb_sys/rocksdb/util/threadpool_imp.cc:312:9\\n 15: _ZN7rocksdb14ThreadPoolImpl4Impl15BGThreadWrapperEPv\\n at workspace/.cargo/git/checkouts/rust-rocksdb-882d3d9019f8b391/1fa430f/librocksdb_sys/rocksdb/util/threadpool_imp.cc:353:15\\n 16: execute_native_thread_routine\\n 17: start_thread\\n 18: __clone3\\n\"] [location=components/raftstore/src/store/compaction_guard.rs:332] [thread_name=] [thread_id=36]\",\"container\":\"tikv\",\"pod\":\"tc-tikv-2\",\"level\":\"FATAL\",\"namespace\":\"endless-ha-test-add-index-tps-7934662-1-149\",\"filename\":\"/localpath/pvc-bb442dbf-6f04-4654-99b3-ec3e72eb38bc_endless-ha-test-add-index-tps-7934662-1-149_tikv-log-tc-tikv-2/tikv.log\"}", "branch": "2d51d3e", "issue_url": "https://github.com/tikv/tikv/issues/18912", "fix_url": "https://github.com/tikv/tikv/pull/18913", "issue_created": "2025-09-01", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "tikv-18983", "system": "tikv", "issue_number": "18983", "lite": false, "title": "tikv panic during sysbench bulk insert", "description": "Bug Report\nWhat version of TiKV are you using?\nsh-5.1# ./tikv-server -V\nTiKV\nRelease Version: 9.0.0-beta.2\nEdition: Community\nGit Commit Hash: 2198165\nGit Commit Branch: HEAD\nUTC Build Time: 2025-09-19 05:14:16\nRust Version: rustc 1.87.0-nightly (96cfc7558 2025-02-27)\nEnable Features: memory-engine pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine trace-async-tasks openssl-vendored\nProfile: dist_release\nsh-5.1#\n\nWhat operating system and CPU are you using?\n12 * 32c128g\n\nSteps to reproduce\n1、sysbench bulk insert\n\nWhat did you expect?\nno panic\n\nWhat did happened?\n2025-09-19 14:58:47.461 {\"namespace\":\"workload-tps-7951356-1-180\",\"log\":\"[lib.rs:555] [\\\"region_id=1259612, peer_id=1259615, idx=9\\\"] [context=\\\"(components/raftstore/src/store/fsm/store.rs:1076) peer_id=>1259615, (components/raftstore/src/store/fsm/store.rs:1076) region_id=>1259612\\\"] [backtrace=\\\" 0: tikv_util::set_panic_hook::{{closure}}\\\\n at workspace/source/tikv/components/tikv_util/src/lib.rs:546:18\\\\n 1: as core::ops::function::Fn>::call\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1986:9\\\\n std::panicking::rust_panic_with_hook\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:839:13\\\\n 2: std::panicking::begin_panic_handler::{{closure}}\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:704:13\\\\n 3: std::sys::backtrace::__rust_end_short_backtrace\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/backtrace.rs:168:18\\\\n 4: rust_begin_unwind\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:695:5\\\\n 5: core::panicking::panic_fmt\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:75:14\\\\n 6: raftstore::store::entry_storage::EntryStorage::term::{{closure}}\\\\n at workspace/source/tikv/components/raftstore/src/store/entry_storage.rs:1119:21\\\\n 7: core::option::Option::unwrap_or_else\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/option.rs:1023:21\\\\n raftstore::store::entry_storage::EntryStorage::term\\\\n at workspace/source/tikv/components/raftstore/src/store/entry_storage.rs:1118:18\\\\n 8: as raft::storage::Storage>::term\\\\n at workspace/source/tikv/components/raftstore/src/store/peer_storage.rs:286:9\\\\n raft::raft_log::RaftLog::term\\\\n at workspace/.cargo/git/checkouts/raft-rs-8d904e7e48a482b3/0d01b20/src/raft_log.rs:144:18\\\\n 9: raftstore::store::peer::Peer::get_index_term\\\\n at workspace/source/tikv/components/raftstore/src/store/peer.rs:1193:15\\\\n raftstore::store::fsm::peer::PeerFsmDelegate::on_raft_gc_log_tick\\\\n at workspace/source/tikv/components/raftstore/src/store/fsm/peer.rs:6221:20\\\\n 10: raftstore::store::fsm::peer::PeerFsmDelegate::handle_msgs\\\\n at workspace/source/tikv/components/raftstore/src/store/fsm/peer.rs:714:40\\\\n 11: as batch_system::batch::PollHandler,raftstore::store::fsm::store::StoreFsm>>::handle_normal\\\\n at workspace/source/tikv/components/raftstore/src/store/fsm/store.rs:1119:9\\\\n 12: batch_system::batch::Poller::poll\\\\n at workspace/source/tikv/components/batch-system/src/batch.rs:458:27\\\\n 13: raftstore::store::worker::refresh_config::PoolController::increase_by::{{closure}}\\\\n at workspace/source/tikv/components/raftstore/src/store/worker/refresh_config.rs:84:21\\\\n ::spawn_wrapper::{{closure}}\\\\n at workspace/source/tikv/components/tikv_util/src/sys/thread.rs:441:13\\\\n std::sys::backtrace::__rust_begin_short_backtrace\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/backtrace.rs:152:18\\\\n 14: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:559:17\\\\n as core::ops::function::FnOnce<()>>::call_once\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:272:9\\\\n std::panicking::try::do_call\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:587:40\\\\n std::panicking::try\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:550:19\\\\n std::panic::catch_unwind\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:359:14\\\\n std::thread::Builder::spawn_unchecked_::{{closure}}\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:557:30\\\\n core::ops::function::FnOnce::call_once{{vtable.shim}}\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5\\\\n 15: as core::ops::function::FnOnce>::call_once\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1972:9\\\\n as core::ops::function::FnOnce>::call_once\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1972:9\\\\n std::sys::pal::unix::thread::Thread::new::thread_start\\\\n at root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/pal/unix/thread.rs:109:17\\\\n 16: start_thread\\\\n 17: __clone\\\\n\\\"] [location=/workspace/source/tikv/components/raftstore/src/store/entry_storage.rs:1119] [thread_name=raftstore-18-0] [thread_id=222]\",\"filename\":\"/localpath/pvc-b759569f-589b-4007-9c7d-1461e70e0227_workload-tps-7951356-1-180_tikv-log-tc-tikv-0/tikv.log\",\"container\":\"tikv\",\"pod\":\"tc-tikv-0\",\"level\":\"FATAL\"}", "branch": "2198165", "issue_url": "https://github.com/tikv/tikv/issues/18983", "fix_url": "https://github.com/tikv/tikv/pull/18984", "issue_created": "2025-09-19", "severity": "Critical", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "tikv-19004", "system": "tikv", "issue_number": "19004", "lite": true, "title": "TiKV panicked during jepsen test ", "description": "Bug Report\nWhat version of TiKV are you using?\nmaster\n\nWhat operating system and CPU are you using?\nk8s\n\nSteps to reproduce\nrun jepsen test\n\nWhat did you expect?\nno panic\n\nWhat did happened?\n[2025/09/20 05:17:24.026 +00:00] [FATAL] [lib.rs:555] [\"assertion failed: self.fsm.peer.pending_remove\"] [context=\"(components/raftstore/src/store/fsm/store.rs:1076) peer_id=>3509, (components/raftstore/src/store/fsm/store.rs:1076) region_id=>3505\"] [backtrace=\" 0: tikv_util::set_panic_hook::{{closure}}\\n at /workspace/source/tikv/components/tikv_util/src/lib.rs:546:18\\n 1: as core::ops::function::Fn>::call\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1986:9\\n std::panicking::rust_panic_with_hook\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:839:13\\n 2: std::panicking::begin_panic_handler::{{closure}}\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:697:13\\n 3: std::sys::backtrace::__rust_end_short_backtrace\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/backtrace.rs:168:18\\n 4: rust_begin_unwind\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:695:5\\n 5: core::panicking::panic_fmt\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:75:14\\n 6: core::panicking::panic\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:145:5\\n 7: raftstore::store::fsm::peer::PeerFsmDelegate::on_significant_msg\\n at /workspace/source/tikv/components/raftstore/src/store/fsm/peer.rs:1637:17\\n 8: raftstore::store::fsm::peer::PeerFsmDelegate::handle_msgs\\n at /workspace/source/tikv/components/raftstore/src/store/fsm/peer.rs:718:49\\n 9: as batch_system::batch::PollHandler,raftstore::store::fsm::store::StoreFsm>>::handle_normal\\n at /workspace/source/tikv/components/raftstore/src/store/fsm/store.rs:1119:9\\n 10: batch_system::batch::Poller::poll\\n at /workspace/source/tikv/components/batch-system/src/batch.rs:458:27\\n 11: raftstore::store::worker::refresh_config::PoolController::increase_by::{{closure}}\\n at /workspace/source/tikv/components/raftstore/src/store/worker/refresh_config.rs:84:21\\n ::spawn_wrapper::{{closure}}\\n at /workspace/source/tikv/components/tikv_util/src/sys/thread.rs:441:13\\n std::sys::backtrace::__rust_begin_short_backtrace\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/backtrace.rs:152:18\\n 12: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:559:17\\n as core::ops::function::FnOnce<()>>::call_once\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:272:9\\n std::panicking::try::do_call\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:587:40\\n std::panicking::try\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:550:19\\n std::panic::catch_unwind\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:359:14\\n std::thread::Builder::spawn_unchecked_::{{closure}}\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:557:30\\n core::ops::function::FnOnce::call_once{{vtable.shim}}\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5\\n 13: as core::ops::function::FnOnce>::call_once\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1972:9\\n as core::ops::function::FnOnce>::call_once\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1972:9\\n std::sys::pal::unix::thread::Thread::new::thread_start\\n at /root/.rustup/toolchains/nightly-2025-02-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/pal/unix/thread.rs:109:17\\n 14: start_thread\\n 15: __clone3\\n\"] [location=/workspace/source/tikv/components/raftstore/src/store/fsm/peer.rs:1637] [thread_name=raftstore-2-0] [thread_id=139]\nThe full logs can be downloaded via this script.", "branch": "fb85c9563caeeac44777a52cb872cb6d84fbc093", "issue_url": "https://github.com/tikv/tikv/issues/19004", "fix_url": "https://github.com/tikv/tikv/pull/19030", "issue_created": "2025-09-26", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "tikv-19220", "system": "tikv", "issue_number": "19220", "lite": false, "title": "load base split can not work when scan table", "description": "Bug Report\nWhat did you do?\n1、create a small table\n2、run oltp_write_only\n3、table full scan\n\nWhat did you expect to see?\nregion can be splited\n\nWhat did you see instead?\nregion can not be splited\n\nWhat version of PD are you using (pd-server -V)?\n./pd-server -V\nRelease Version: v9.0.0-beta.2.pre-223-gaef91a5\nEdition: Community\nKernel Type: Classic\nGit Commit Hash: aef91a5ee6d6747b611f78f3874babd06af2d67d\nGit Branch: HEAD\nUTC Build Time: 2025-12-11 01:57:48\n2025-12-11T22:42:01.516+0800 INFO k8s/client.go:141 it should be noted that a long-running command will not be interrupted even the use case has ended. For more information, please refer to https://github.com/pingcap/test-infra/discussions/129", "branch": "aef91a5ee6d6747b611f78f3874babd06af2d67d", "issue_url": "https://github.com/tikv/tikv/issues/19220", "fix_url": "https://github.com/tikv/tikv/pull/19223", "issue_created": "2025-12-18", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "tikv-19238", "system": "tikv", "issue_number": "19238", "lite": false, "title": "Log Backup may get stuck due to async lock held across .await", "description": "Bug Report\nUnder certain configurations, Log Backup may get permanently stuck.\n\nOnce this happens:\n\nLog backup no longer makes progress, no related backup log output\nPause/Stop task commands do not work\nThis issue is strongly correlated with holding an async lock across .await, which may stall the Tokio runtime when thread resources are constrained.\n\nWhat version of TiKV are you using?\nv8.5.3\n\nWhat operating system and CPU are you using?\nN/A\n\nSteps to reproduce\nIt's not easy to reproduce, but a hypothesis version should be\n\nUse a small Tokio runtime thread pool\n• e.g. reduce [log-backup] num.threads to a small number (1–2)\nConfigure log backup with a short flush interval\nStart normal write workload and wait\nWhat did you expect?\nLog backup works normally.\n\nWhat did happened?\nLog backup flush stops making progress without reporting any error.\n\nWhen this happens:\n\nLog backup no longer advances\nQuerying /async-tasks shows that async tasks are blocked on S3-related operations\n- These S3 operations are configured with Tokio timeouts, but:\n- The timeouts do not trigger\nPause / control operations do not work", "branch": "v8.5.3", "issue_url": "https://github.com/tikv/tikv/issues/19238", "fix_url": "https://github.com/tikv/tikv/pull/19252", "issue_created": "2025-12-26", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Medium", "distributed": false, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-2581", "system": "zookeeper", "issue_number": "2581", "lite": true, "title": "Not handled NullPointerException while creating key manager and trustManager", "description": "Not handled NullPointerException while creating key manager and trustManager:-\n\n2016-09-14 13:35:23,488 [myid:1] - ERROR [CommitProcWorkThread-1:X509AuthenticationProvider@78] - Failed to create key manager\norg.apache.zookeeper.common.X509Exception$KeyManagerException: java.lang.NullPointerException\nat org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:129)\nat org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:75)\nat org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42)\nat org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68)\nat org.apache.zookeeper.server.PrepRequestProcessor.checkACL(PrepRequestProcessor.java:319)\nat org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:324)\nat org.apache.zookeeper.server.quorum.CommitProcessor$CommitWorkRequest.doWork(CommitProcessor.java:296)\nat org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162)\nat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)\nat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\nat java.lang.Thread.run(Thread.java:745)\nCaused by: java.lang.NullPointerException\nat org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:113)\n... 10 more\n2016-09-14 13:35:23,489 [myid:1] - ERROR [CommitProcWorkThread-1:X509AuthenticationProvider@90] - Failed to create trust manager\norg.apache.zookeeper.common.X509Exception$TrustManagerException: java.lang.NullPointerException\nat org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:158)\nat org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:87)\nat org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42)\nat org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68)\nat org.apache.zookeeper.server.PrepRequestProcessor.checkACL(PrepRequestProcessor.java:319)\nat org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:324)\nat org.apache.zookeeper.server.quorum.CommitProcessor$CommitWorkRequest.doWork(CommitProcessor.java:296)\nat org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162)\nat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)\nat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\nat java.lang.Thread.run(Thread.java:745)\nCaused by: java.lang.NullPointerException\nat org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:143)\n... 10 more", "branch": "release-3.5.1", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-2581", "fix_url": "https://github.com/apache/zookeeper/commit/88c1c93", "issue_created": "2016-09-14", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "zookeeper-2623", "system": "zookeeper", "issue_number": "2623", "lite": false, "title": "CheckVersion outside of Multi causes NullPointerException", "description": "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?\n\nHere are the server logs:\n\nAccepted socket connection from /0:0:0:0:0:0:0:1:51737\nSession establishment request from client /0:0:0:0:0:0:0:1:51737 client's lastZxid is 0x0\nConnection request from old client /0:0:0:0:0:0:0:1:51737; will be dropped if server is in r-o mode\nClient attempting to establish new session at /0:0:0:0:0:0:0:1:51737\n:Fsessionid:0x10025651faa0000 type:createSession cxid:0x0 zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a\nProcessing request:: sessionid:0x10025651faa0000 type:createSession cxid:0x0 zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a\nGot zxid 0x60000065e expected 0x1\nCreating new log file: log.60000065e\nCommitting request:: sessionid:0x10025651faa0000 type:createSession cxid:0x0 zxid:0x60000065e txntype:-10 reqpath:n/a\nProcessing request:: sessionid:0x10025651faa0000 type:createSession cxid:0x0 zxid:0x60000065e txntype:-10 reqpath:n/a\n:Esessionid:0x10025651faa0000 type:createSession cxid:0x0 zxid:0x60000065e txntype:-10 reqpath:n/a\nsessionid:0x10025651faa0000 type:createSession cxid:0x0 zxid:0x60000065e txntype:-10 reqpath:n/a\nAdd a buffer to outgoingBuffers, sk sun.nio.ch.SelectionKeyImpl@28e9f397 is valid: true\nEstablished session 0x10025651faa0000 with negotiated timeout 20000 for client /0:0:0:0:0:0:0:1:51737\n:Fsessionid:0x10025651faa0000 type:check cxid:0x1 zxid:0xfffffffffffffffe txntype:unknown reqpath:/\nProcessing request:: sessionid:0x10025651faa0000 type:check cxid:0x1 zxid:0xfffffffffffffffe txntype:unknown reqpath:/\nProcessing request:: sessionid:0x10025651faa0000 type:check cxid:0x1 zxid:0xfffffffffffffffe txntype:unknown reqpath:/\nException causing close of session 0x10025651faa0000: Connection reset by peer\n:Esessionid:0x10025651faa0000 type:check cxid:0x1 zxid:0xfffffffffffffffe txntype:unknown reqpath:/\nIOException stack trace\njava.io.IOException: Connection reset by peer\n\tat sun.nio.ch.FileDispatcherImpl.read0(Native Method)\n\tat sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)\n\tat sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)\n\tat sun.nio.ch.IOUtil.read(IOUtil.java:197)\n\tat sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)\n\tat org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:320)\n\tat org.apache.zookeeper.server.NIOServerCnxnFactory$IOWorkRequest.doWork(NIOServerCnxnFactory.java:530)\n\tat org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\n\tat java.lang.Thread.run(Thread.java:745)\nUnexpected exception\njava.lang.NullPointerException\n\tat org.apache.zookeeper.server.ZKDatabase.addCommittedProposal(ZKDatabase.java:252)\n\tat org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:127)\n\tat org.apache.zookeeper.server.quorum.CommitProcessor$CommitWorkRequest.doWork(CommitProcessor.java:362)\n\tat org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\n\tat java.lang.Thread.run(Thread.java:745)\nCommitting request:: sessionid:0x10025651faa0000 type:error cxid:0x1 zxid:0x60000065f txntype:-1 reqpath:n/a\nUnregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id1,name1=replica.1,name2=Follower,name3=Connections,name4=\"0:0:0:0:0:0:0:1\",name5=0x10025651faa0000]\nException thrown by downstream processor, unable to continue.\nCommitProcessor exited loop!\nClosed socket connection for client /0:0:0:0:0:0:0:1:51737 which had sessionid 0x10025651faa0000\nAnd here's a one-liner to repro, which does a ConnectRequest followed by a CheckVersion(path=\"/\", version=89235}:\n\necho AAAALAAAAAAAAAAAAAAAAAAAJxAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAEQAAAAEAAAANAAAAAS8AAVyT | base64 --decode | nc localhost 2181 >/dev/null\nThis is against master as of a couple of weeks ago (f78061a). I haven't checked to see which versions are affected.", "branch": "release-3.9.0", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-2623", "fix_url": "https://github.com/apache/zookeeper/pull/1988", "issue_created": "2016-10-28", "severity": "Critical", "root_cause_type": "Error handling", "bug_complexity": "Hard", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "zookeeper-2775", "system": "zookeeper", "issue_number": "2775", "lite": false, "title": "ZK Client not able to connect with Xid out of order error", "description": "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.\n\nLogs:\n\nunexpected error, closing socket connection and attempting reconnect | org.apache.zookeeper.ClientCnxn (ClientCnxn.java:1447)\njava.io.IOException: Xid out of order. Got Xid 52 with err 0 expected Xid 53 for a packet with details: clientPath:null serverPath:null finished:false header:: 53,101 replyHeader:: 0,0,-4 request:: 12885502275,v\n\n{'/app1/controller,'/app1/config/changes}\n,v{},v\n\n{'/app1/config/changes}\nresponse:: null\nat org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:996)\nat org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:101)\nat org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:370)\nat org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1426)\n\nunexpected error, closing socket connection and attempting reconnect\njava.io.IOException: Nothing in the queue, but got 1\nat org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:983)\nat org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:101)\nat org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:370)\nat org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1426)\n\nAnalysis:\n1) First time Client fails to do SASL login due to network unreachable problem.\n2017-03-29 10:03:59,377 | WARN | [main-SendThread(192.168.130.8:24002)] | SASL configuration failed: javax.security.auth.login.LoginException: Network is unreachable (sendto failed) Will continue connection to Zookeeper server without SASL authentication, if Zookeeper server allows it. | org.apache.zookeeper.ClientCnxn (ClientCnxn.java:1307)\nHere the boolean saslLoginFailed becomes true.\n\n2) After some time network connection is recovered and client is successully able to login but still the boolean saslLoginFailed is not reset to false.\n\n3) Now SASL negotiation between client and server start happening and during this time no user request will be sent. ( As the socket channel will be closed for write till sasl negotiation complets)\n4) Now response from server for SASL packet will be processed by the client and client assumes that tunnelAuthInProgress() is finished ( method checks for saslLoginFailed boolean Since the boolean is true it assumes its done.) and tries to process the packet as a other packet and will result in above errors.\n\nSolution: Reset the saslLoginFailed boolean every time before client login", "branch": "release-3.5.3", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-2775", "fix_url": "https://github.com/apache/zookeeper/commit/0026e27", "issue_created": "2017-05-05", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "zookeeper-2836", "system": "zookeeper", "issue_number": "2836", "lite": false, "title": "QuorumCnxManager.Listener Thread Better handling of SocketTimeoutException", "description": "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: $/$:3888_\" , Once server nodes reache this state and we restart or add a new node ,it fails to join cluster and logs 'WARN QuorumPeer/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@383 - Cannot open channel to 3 at election address $/$:3888' .\n\nAs there is no timeout specified for ServerSocket it should never timeout but there are some already discussed issues where people have seen this issue and added checks for SocketTimeoutException explicitly like https://issues.apache.org/jira/browse/KARAF-3325 .\n\nI think we need to handle SocketTimeoutException on similar lines for zookeeper as well", "branch": "release-3.5.3", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-2836", "fix_url": "https://github.com/apache/zookeeper/pull/336", "issue_created": "2017-07-04", "severity": "Critical", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-2845", "system": "zookeeper", "issue_number": "2845", "lite": true, "title": "Data inconsistency issue due to retain database in leader election", "description": "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.\n\nIf snapshot is ahead of txn file, since the SyncRequestProcessor queue will be drained during shutdown, the snapshot and txn file will keep consistent before leader election happening, so this is not an issue.\n\nBut if txn is ahead of snapshot, it's possible that the ensemble will have data inconsistent issue, here is the simplified scenario to show the issue:\n\nLet's say we have a 3 servers in the ensemble, server A and B are followers, and C is leader, and all the snapshot and txn are up to T0:\n1. A new request reached to leader C to create Node N, and it's converted to txn T1\n2. Txn T1 was synced to disk in C, but just before the proposal reaching out to the followers, A and B restarted, so the T1 didn't exist in A and B\n3. A and B formed a new quorum after restart, let's say B is the leader\n4. C changed to looking state due to no enough followers, it will sync with leader B with last Zxid T0, which will have an empty diff sync\n5. Before C take snapshot it restarted, it replayed the txns on disk which includes T1, now it will have Node N, but A and B doesn't have it.\n\nAlso I included the a test case to reproduce this issue consistently.\n\nWe have a totally different RetainDB version which will avoid this issue by doing consensus between snapshot and txn files before leader election, will submit for review.", "branch": "release-3.5.3", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-2845", "fix_url": "https://github.com/apache/zookeeper/commit/ffb81b9", "issue_created": "2017-07-14", "severity": "Critical", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-2959", "system": "zookeeper", "issue_number": "2959", "lite": false, "title": "ignore accepted epoch and LEADERINFO ack from observers when a newly elected leader computes new epoch", "description": "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.\n\nThe computation will get an outcome once :\n\n- The leader has call method \"getEpochToPropose\"\n- The number of all reporters is greater than half of participants.\n\nThe problem is, an observer server will also send its accepted epoch to the leader, while this procedure treat observers as participants.\n\nSupposed that the cluster consists of 1 leader, 2 followers and 1 observer, and now the leader and the observer have reported their accepted epochs while neither of the followers has. Thus, the connectingFollowers set consists of two elements, resulting in a size of 2, which is greater than half quorum, namely, 2. Then QuorumVerifier#containsQuorum will return true, because it does not check whether the elements of the parameter are participants.\n\nThe same flaw exists in org.apache.zookeeper.server.quorum.Leader#waitForEpochAck", "branch": "release-3.5.3", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-2959", "fix_url": "https://github.com/apache/zookeeper/commit/088dfdf", "issue_created": "2017-12-20", "severity": "Blocker", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": true, "contains_analysis": true, "analysis_removed": "Partly Removed", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-2960", "system": "zookeeper", "issue_number": "2960", "lite": false, "title": "The dataDir and dataLogDir are used opposingly", "description": "_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.\n\nConfiguration file has:\n\n$ grep -i data /etc/zookeeper/zoo.cfg \ndataLogDir=/var/lib/zookeeper/datalog\ndataDir=/var/lib/zookeeper/data\nBut runtime configuration has:\n\n$ echo conf | nc localhost 2181 | grep -i data\ndataDir=/var/lib/zookeeper/datalog/version-2\ndataLogDir=/var/lib/zookeeper/data/version-2\nAlso, I got this in the debug logs, so clearly some parts of the server confuse things.\n\n[PurgeTask:FileTxnSnapLog@79] - Opening datadir:/var/lib/zookeeper/datalog snapDir:/var/lib/zookeeper/data\n[main:FileTxnSnapLog@79] - Opening datadir:/var/lib/zookeeper/data snapDir:/var/lib/zookeeper/datalog\nI tried to look in the code for wrong uses of the directories. I only found ZookeeperServer.java is passing the arguments to FileTxnSnapLog in the wrong order, but the code comment says that this is legacy only for tests, so I assume it isn't the cause for my case.", "branch": "release-3.4.11", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-2960", "fix_url": "https://github.com/apache/zookeeper/pull/441", "issue_created": "2017-12-22", "severity": "Critical", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-2982", "system": "zookeeper", "issue_number": "2982", "lite": true, "title": "Re-try DNS hostname -> IP resolution", "description": "ZOOKEEPER-1506 fixed a DNS resolution issue in 3.4. Some portions of the fix haven't yet been ported to 3.5.\n\nTo 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 example, deploying ZK 3.5 to Kubernetes using a StatefulSet plus a Service (headless) may fail because the DNS records are created lazily.\n\n2018-02-18 09:11:22,583 [myid:0] - WARN [QuorumPeer[myid=0](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Follower@95] - Exception when following the leader\njava.net.UnknownHostException: zk-2.zk.default.svc.cluster.local\n at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)\n at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)\n at java.net.Socket.connect(Socket.java:589)\n at org.apache.zookeeper.server.quorum.Learner.sockConnect(Learner.java:227)\n at org.apache.zookeeper.server.quorum.Learner.connectToLeader(Learner.java:256)\n at org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:76)\n at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1133)\nIn the above example, the address `zk-2.zk.default.svc.cluster.local` was not resolvable when the server started, but became resolvable shortly thereafter. The server should eventually succeed but doesn't.", "branch": "release-3.5.3", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-2982", "fix_url": "https://github.com/apache/zookeeper/pull/513", "issue_created": "2018-02-19", "severity": "Blocker", "root_cause_type": "Error handling", "bug_complexity": "Hard", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "zookeeper-3218", "system": "zookeeper", "issue_number": "3218", "lite": false, "title": "zk server reopened，the interval for observer connect to the new leader is too long，then session expired", "description": "two participants、one observer，zkclient connect to observer。\n\nThen，close the two participants，the zookeeper server cloesed\n\nTen seconds later，reopen the two participants，and leader selected\n\n----------------------------------------------------------------------------\n\nBut the observer can't connect to the new leader immediately。Because in lookForLeader, the observer use blockingQueue(recvqueue) to offer/poll notifications，when the recvqueue is empty，poll from recvqueue will be blocked，and timeout is 200ms，400ms，800ms....60s。\n\nFor example，09:59:59 observer poll notification，recvqueue was empty and timeout was 60s；10:00:00 two participants reopened and reselected；10:00:59 observer polled notification，connected to the new leader\n\nBut the maxSessionTimeout default to 40s。The session expired\n\n-----------------------------------------------------------------------------\n\nPlease improve it：observer should connect to the new leader as soon as possible", "branch": "release-3.5.5", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-3218", "fix_url": "https://github.com/apache/zookeeper/pull/747", "issue_created": "2018-12-17", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-3642", "system": "zookeeper", "issue_number": "3642", "lite": false, "title": "Data inconsistency when the leader crashes right after sending SNAP sync", "description": "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)\n\nA new leader will get elected, and it will resync our learner again immediately. But this time, it will use the incremental DIFF method, starting from Zxid X. A DIFF-based resync does not trigger snapshots, so the learner is still holding the original snapshot purely in memory. If the learner restarts after that, it will silently lose all the data up to Zxid X.\n\nAn easy way to reproduce is to insert System.exit into LearnerHandler.java right before sending the NEWLEADER message (on the one instance that is currently running the leader, but not the others):\n\n LOG.debug(\"Sending NEWLEADER message to \" + sid);\n+ if (leader.self.getId() == 1 && sid == 3) {\n+ LOG.debug(\"Bail when server.1 resyncs server.3\");\n+ System.exit(0);\n+ }\nIf I remember right, the repro steps are as follows. Run with that patch in a 4-instance ensemble where server.3 is an Observer, the rest are voting members, and server.1 is the current Leader. Start server.3 after the other instances are up. It will get the initial snapshot from server.1 and server.1 will stop immediately because of the patch. Say, server.2 takes over as the new Leader. Server.3 will receive a Diff resync from server.2, but will skip persisting the snapshot. A subsequent restart of server.3 will make that instance come up with a blank data tree.\n\nThe above steps assumed that server.3 is an Observer, but it can presumably happen for voting members too. Just need a 5-instance ensemble.", "branch": "release-3.5.6", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-3642", "fix_url": "https://github.com/apache/zookeeper/commit/161e505", "issue_created": "2019-12-09", "severity": "Major", "root_cause_type": "Concurrency", "bug_complexity": "Hard", "distributed": true, "contains_analysis": true, "analysis_removed": "Partly Removed", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-3644", "system": "zookeeper", "issue_number": "3644", "lite": false, "title": "Data loss after upgrading standalone ZK server 3.4.14 to 3.5.6 with snapshot.trust.empty=true", "description": "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.\n\nSteps to reproduce:\n\nStart a single node ZK 3.4.14 server and create few znodes\nUpgrade the server to 3.5.6 with snapshot.trust.empty=true config\ntry to list the znodes using zkShell\nLooking into the source code, looks like we are not reading transaction log if there are no snapshot files and snapshot.trust.empty is set to true.\n\nZK 3.5.6 logs:\n\n[2019-12-07 12:13:35,007] INFO Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 60000 datadir /var/lib/zookeeper/version-2 snapdir /var/lib/zookeeper/version-2\n (org.apache.zookeeper.server.ZooKeeperServer)\n[2019-12-07 12:13:35,012] INFO Using org.apache.zookeeper.server.NIOServerCnxnFactory as server connection factory (org.apache.zookeeper.server.ServerCnxnFactory)\n[2019-12-07 12:13:35,014] INFO Configuring NIO connection handler with 10s sessionless connection timeout, 1 selector thread(s), 12 worker threads, and 64 kB direct buffers. (org.apache\n.zookeeper.server.NIOServerCnxnFactory)\n[2019-12-07 12:13:35,017] INFO binding to port 0.0.0.0/0.0.0.0:2181 (org.apache.zookeeper.server.NIOServerCnxnFactory)\n[2019-12-07 12:13:35,027] INFO zookeeper.snapshotSizeFactor = 0.33 (org.apache.zookeeper.server.ZKDatabase)\n[2019-12-07 12:13:35,029] DEBUG Created new input stream /var/lib/zookeeper/version-2/log.1 (org.apache.zookeeper.server.persistence.FileTxnLog)\n[2019-12-07 12:13:35,031] DEBUG Created new input archive /var/lib/zookeeper/version-2/log.1 (org.apache.zookeeper.server.persistence.FileTxnLog)\n[2019-12-07 12:13:35,035] DEBUG EOF exception java.io.EOFException: Failed to read /var/lib/zookeeper/version-2/log.1 (org.apache.zookeeper.server.persistence.FileTxnLog)\n[2019-12-07 12:13:35,035] WARN No snapshot found, but there are log entries. This should only be allowed during upgrading. (org.apache.zookeeper.server.persistence.FileTxnSnapLog)\n[2019-12-07 12:13:35,035] INFO Snapshotting: 0x0 to /var/lib/zookeeper/version-2/snapshot.0 (org.apache.zookeeper.server.persistence.FileTxnSnapLog)\n[2019-12-07 12:13:35,036] INFO Snapshotting: 0x0 to /var/lib/zookeeper/version-2/snapshot.0 (org.apache.zookeeper.server.persistence.FileTxnSnapLog)\n[2019-12-07 12:13:35,050] INFO Using checkIntervalMs=60000 maxPerMinute=10000 (org.apache.zookeeper.server.ContainerManager)\n[2019-12-07 12:15:07,137] DEBUG Accepted socket connection from /127.0.0.1:38888 (org.apache.zookeeper.server.NIOServerCnxnFactory)\n[2019-12-07 12:15:07,144] DEBUG Session establishment request from client /127.0.0.1:38888 client's lastZxid is 0x0 (org.apache.zookeeper.server.ZooKeeperServer)\n[2019-12-07 12:15:07,145] DEBUG Adding session 0x100006e15fb0000 (org.apache.zookeeper.server.SessionTrackerImpl)\n[2019-12-07 12:15:07,148] TRACE SessionTrackerImpl — Adding session 0x100006e15fb0000 30000 (org.apache.zookeeper.server.SessionTrackerImpl)\n[2019-12-07 12:15:07,149] DEBUG Client attempting to establish new session: session = 0x100006e15fb0000, zxid = 0x0, timeout = 30000, address = /127.0.0.1:38888 (org.apache.zookeeper.server.ZooKeeperServer)\n[2019-12-07 12:15:07,155] TRACE :Psessionid:0x100006e15fb0000 type:createSession cxid:0x0 zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a (org.apache.zookeeper.server.PrepRequestProcessor)\n[2019-12-07 12:15:07,155] TRACE SessionTrackerImpl — Existing session 0x100006e15fb0000 30000 (org.apache.zookeeper.server.SessionTrackerImpl)\n[2019-12-07 12:15:07,155] INFO Creating new log file: log.1 (org.apache.zookeeper.server.persistence.FileTxnLog)\n[2019-12-07 12:15:07,170] DEBUG Processing request:: sessionid:0x100006e15fb0000 type:createSession cxid:0x0 zxid:0x1 txntype:-10 reqpath:n/a (org.apache.zookeeper.server.FinalRequestProcessor)", "branch": "release-3.5.6", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-3644", "fix_url": "https://github.com/apache/zookeeper/commit/a314855", "issue_created": "2019-12-10", "severity": "Blocker", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": false, "contains_analysis": true, "analysis_removed": "No", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-3656", "system": "zookeeper", "issue_number": "3656", "lite": false, "title": "SyncRequestProcessor doesn't update lastFlushTime correctly on observers", "description": "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.\n\nThis can cause observers to fall behind and their sync queue to grow indefinitely.", "branch": "release-3.6.3", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-3656", "fix_url": "https://github.com/apache/zookeeper/pull/1189", "issue_created": "2019-12-19", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Easy", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-3769", "system": "zookeeper", "issue_number": "3769", "lite": false, "title": "fast leader election does not end if leader is taken down", "description": "In a cluster with three nodes, node3 is the leader and the other nodes are followers.\n\nIf I stop node3, the other two nodes do not finish the leader election.\n\nThis is happening with ZK 3.5.7, openjdk version \"12.0.2\" 2019-07-16, and this config\n\n \n\ntickTime=2000\ninitLimit=30\nsyncLimit=3\ndataDir=/company/service/data\ndataLogDir=/company/service/log\nclientPort=2181\nsnapCount=100000\nautopurge.snapRetainCount=3\nautopurge.purgeInterval=1\nskipACL=yes\npreAllocSize=65536\nmaxClientCnxns=0\n4lw.commands.whitelist=*\nadmin.enableServer=false\n\nserver.1=companydemo1.snc4.companyinc.com:3000:4000\nserver.2=companydemo2.snc4.companyinc.com:3000:4000\nserver.3=companydemo3.snc4.companyinc.com:3000:4000\n\n \n\nCould you have a look at the logs and help me figure this out? It seems like node 1 is not getting notifications back from node2, but I don't see anything wrong with the network so I am wondering if bugs like ZOOKEEPER-3756 could be causing it.\n\n \n\nIn the logs, node3 is killed at 11:17:14\n\nnode2 is killed at 11:17:50 2 and node 1 at 11:18:02 ", "branch": "release-3.5.7", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-3769", "fix_url": "https://github.com/apache/zookeeper/commit/68466c8", "issue_created": "2020-03-24", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": false, "num_artifacts": 3} {"instance_id": "zookeeper-3829", "system": "zookeeper", "issue_number": "3829", "lite": false, "title": "Zookeeper refuses request after node expansion", "description": "It's easy to reproduce this bug.\n\n//代码占位符\n \nStep 1. Deploy 3 nodes A,B,C with configuration A,B,C .\nStep 2. Deploy node ` D` with configuration `A,B,C,D` , cluster state is ok now.\nStep 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 command like `ls /` will be blocked.\n\nStep 4. Restart nodes D, cluster state is back to normal now.\n \n \n\nWe have looked into the code of 3.5.6 version, and we found it may be the issue of `workerPool` .\n\nThe `CommitProcessor` shutdown and make `workerPool` shutdown, but `workerPool` still exists. It will never work anymore, yet the cluster still thinks it's ok.\n\n \n\nI think the bug may still exist in master branch.\n\nWe have tested it in our machines by reset the `workerPool` to null. If it's ok, please assign this issue to me, and then I'll create a PR. ", "branch": "release-3.6.1", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-3829", "fix_url": "https://github.com/apache/zookeeper/commit/48f037f", "issue_created": "2020-05-15", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Hard", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 2} {"instance_id": "zookeeper-3988", "system": "zookeeper", "issue_number": "3988", "lite": false, "title": "org.apache.zookeeper.server.NettyServerCnxn.receiveMessage throws NullPointerException", "description": "While upgrading K8S cluster, container running zookeeper will rollover one by one.\nDuring this rollover, Null Pointer Exception was observed as below.\n\nINFO [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):Follower@292] - shutdown FollowerINFO [QuorumPeer[myid=1](plain=0.0.0.0:2181)(secure=0.0.0.0:2281):LearnerZooKeeperServer@160] - Shutting downINFO [QuorumPeer[myid=1](plain=0.0.0.0:2181)(secure=0.0.0.0:2281):ZooKeeperServer@784] - shutting downINFO [QuorumPeer[myid=1](plain=0.0.0.0:2181)(secure=0.0.0.0:2281):RequestThrottler@244] - Shutting downINFO [RequestThrottler:RequestThrottler@205] - Draining request throttler queueINFO [RequestThrottler:RequestThrottler@181] - RequestThrottler shutdown. Dropped 0 requestsINFO [QuorumPeer[myid=1](plain=0.0.0.0:2181)(secure=0.0.0.0:2281):FollowerRequestProcessor@148] - Shutting downINFO [QuorumPeer[myid=1](plain=0.0.0.0:2181)(secure=0.0.0.0:2281):CommitProcessor@617] - Shutting downINFO [FollowerRequestProcessor:1:FollowerRequestProcessor@112] - FollowerRequestProcessor exited loop!INFO [CommitProcessor:1:CommitProcessor@406] - CommitProcessor exited loop!INFO [QuorumPeer[myid=1](plain=0.0.0.0:2181)(secure=0.0.0.0:2281):FinalRequestProcessor@662] - shutdown of request processor completeERROR [nioEventLoopGroup-4-22:NettyServerCnxnFactory$CnxnChannelHandler@329] - Unexpected exception in receivejava.lang.NullPointerException: null at org.apache.zookeeper.server.NettyServerCnxn.receiveMessage(NettyServerCnxn.java:515) ~[zookeeper-3.6.1.jar:3.6.1] at org.apache.zookeeper.server.NettyServerCnxn.processMessage(NettyServerCnxn.java:365) ~[zookeeper-3.6.1.jar:3.6.1] at org.apache.zookeeper.server.NettyServerCnxnFactory$CnxnChannelHandler.channelRead(NettyServerCnxnFactory.java:326) [zookeeper-3.6.1.jar:3.6.1] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [netty-common-4.1.48.Final.jar:4.1.48.Final] at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.48.Final.jar:4.1.48.Final] at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.48.Final.jar:4.1.48.Final] at java.lang.Thread.run(Thread.java:834) [?:?]WARN [nioEventLoopGroup-4-22:NettyServerCnxnFactory$CnxnChannelHandler@273] - Exception caughtjava.lang.NullPointerException: null at org.apache.zookeeper.server.NettyServerCnxn.receiveMessage(NettyServerCnxn.java:515) ~[zookeeper-3.6.1.jar:3.6.1] at org.apache.zookeeper.server.NettyServerCnxn.processMessage(NettyServerCnxn.java:365) ~[zookeeper-3.6.1.jar:3.6.1] at org.apache.zookeeper.server.NettyServerCnxnFactory$CnxnChannelHandler.channelRead(NettyServerCnxnFactory.java:326) ~[zookeeper-3.6.1.jar:3.6.1] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) [netty-transport-4.1.48.Final.jar:4.1.48.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [netty-common-4.1.48.Final.jar:4.1.48.Final] at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.48.Final.jar:4.1.48.Final] at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.48.Final.jar:4.1.48.Final] at java.lang.Thread.run(Thread.java:834) [?:?] \nExpectation: This scenario should be handled and application should not throw such Null Pointer exception.", "branch": "release-3.7.0", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-3988", "fix_url": "https://github.com/apache/zookeeper/commit/56f807f", "issue_created": "2020-11-02", "severity": "Major", "root_cause_type": "Error handling", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0} {"instance_id": "zookeeper-4699", "system": "zookeeper", "issue_number": "4699", "lite": false, "title": "zh->hostname heap-use-after-free in zookeeper_interest", "description": "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:\n// NOTE: guard access to{hostname, addr_cur, addrs, addrs_old, addrs_new}lock_reconfig(zh);\n\nin the mean while the io thread will call zoo_interest function and access zh->hostname in log: LOG_WARN(LOGCALLBACK(zh), \"Delaying connection after exhaustively trying all servers [%s]\",zh->hostname); without any lock...\n\n \n\n \n\nstack:\n\n{{=================================================================\n==450==ERROR: AddressSanitizer: heap-use-after-free on address 0x6030004fcbd0 at pc 0x7fbc74e9a5ce bp 0x7fbc3ebf4060 sp 0x7fbc3ebf3810\nREAD of size 2 at 0x6030004fcbd0 thread T98\n#0 0x7fbc74e9a5cd (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x8a5cd)\n#1 0x7fbc74e9c61d in __interceptor_vsnprintf (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x8c61d)\n#2 0x55e1ced0cdd6 in log_message (/opt/tiger/{}{}/deploy/bin/{}{}+0x1906dd6)\n#3 0x55e1cecfc578 in zookeeper_interest (/opt/tiger/{}{}/deploy/bin/{}{}+0x18f6578)\n#4 0x55e1ced0f0b4 in do_io (/opt/tiger/{}{}/deploy/bin/{}{}+0x19090b4)\n#5 0x7fbc74bfa4a3 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x74a3)\n#6 0x7fbc73656d0e in __clone (/lib/x86_64-linux-gnu/libc.so.6+0xe8d0e)\n\n0x6030004fcbd0 is located 0 bytes inside of 20-byte region [0x6030004fcbd0,0x6030004fcbe4)\nfreed by thread T100 here:\n#0 0x7fbc74ed1a10 in free (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1a10)\n#1 0x55e1cecf9e14 in zoo_set_servers (/opt/tiger/{}{}/deploy/bin/{}{}+0x18f3e14)\n#5 0x7fbc74bfa4a3 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x74a3)\n\npreviously allocated by thread T100 here:\n#0 0x7fbc74e67f30 in strdup (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x57f30)\n#1 0x55e1cecf9e20 in zoo_set_servers (/opt/tiger/{}{}/deploy/bin/{}{}+0x18f3e20)\n#5 0x7fbc74bfa4a3 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x74a3)\n\nThread T98 created by T0 here:\n#0 0x7fbc74e40f59 in __interceptor_pthread_create (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x30f59)\n#1 0x55e1ced0ea97 in start_threads (/opt/tiger/{}{}/deploy/bin/{}{}+0x1908a97)\n#2 0x55e1ced0ed11 in adaptor_init (/opt/tiger/{}{}/deploy/bin/{}{}+0x1908d11)\n#3 0x55e1cecf9c9c in zookeeper_init_internal (/opt/tiger/{}{}/deploy/bin/{}{}+0x18f3c9c)\n#4 0x55e1cecf9d38 in zookeeper_init (/opt/tiger/{}{}/deploy/bin/{}{}+0x18f3d38)\n#12 0x55e1ce2f2097 in main /tmp/{}{}/{}{}/{}*/main.cc:148\n#13 0x7fbc7358e2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0)\n\nThread T100 created by T0 here:\n#0 0x7fbc74e40f59 in __interceptor_pthread_create (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x30f59)\n#8 0x55e1ce2f2097 in main /tmp/{}{}/{}{}/{}*/main.cc:148\n#9 0x7fbc7358e2e0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202e0)\n\nSUMMARY: AddressSanitizer: heap-use-after-free (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x8a5cd)\nShadow bytes around the buggy address:\n0x0c0680097920: 00 00 00 07 fa fa 00 00 00 07 fa fa fd fd fd fd\n0x0c0680097930: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n0x0c0680097940: fa fa fa fa 00 00 00 07 fa fa 00 00 00 07 fa fa\n0x0c0680097950: 00 00 00 07 fa fa fa fa fa fa fa fa 00 00 00 07\n0x0c0680097960: fa fa fa fa fa fa fa fa fa fa fa fa fa fa 00 00\n=>0x0c0680097970: 00 07 fa fa fa fa fa fa fa fa[fd]fd fd fa fa fa\n0x0c0680097980: fd fd fd fa fa fa 00 00 00 07 fa fa fd fd fd fd\n0x0c0680097990: fa fa fa fa fa fa fa fa 00 00 00 07 fa fa 00 00\n0x0c06800979a0: 00 07 fa fa fd fd fd fd fa fa 00 00 00 07 fa fa\n0x0c06800979b0: fa fa fa fa fa fa fa fa fa fa fa fa fd fd fd fd\n0x0c06800979c0: fa fa fd fd fd fd fa fa fa fa fa fa fa fa fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\nAddressable: 00\nPartially addressable: 01 02 03 04 05 06 07\nHeap left redzone: fa\nHeap right redzone: fb\nFreed heap region: fd\nStack left redzone: f1\nStack mid redzone: f2\nStack right redzone: f3\nStack partial redzone: f4\nStack after return: f5\nStack use after scope: f8\nGlobal redzone: f9\nGlobal init order: f6\nPoisoned by user: f7\nContainer overflow: fc\nArray cookie: ac\nIntra object redzone: bb\nASan internal: fe\nLeft alloca redzone: ca\nRight alloca redzone: cb}}", "branch": "release-3.8.1", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-4699", "fix_url": "https://github.com/apache/zookeeper/pull/2138", "issue_created": "2023-05-24", "severity": "Blocker", "root_cause_type": "Concurrency", "bug_complexity": "Easy", "distributed": true, "contains_analysis": true, "analysis_removed": "No", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-4761", "system": "zookeeper", "issue_number": "4761", "lite": false, "title": "Cli tool read saved clientid fail", "description": "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.", "branch": "release-3.7.0", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-4761", "fix_url": "https://github.com/apache/zookeeper/pull/2079", "issue_created": "2023-10-16", "severity": "Major", "root_cause_type": "Logic", "bug_complexity": "Medium", "distributed": false, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": false, "contains_stack_traces": false, "num_artifacts": 0} {"instance_id": "zookeeper-4921", "system": "zookeeper", "issue_number": "4921", "lite": false, "title": "Zookeeper Client 3.9.3 Fails to Reconnect After Network Failures", "description": "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.\n\nApr 23, 2025 10:19:23 AM com.twitter.finagle.common.zookeeper.ZooKeeperClient$3 process\nINFO: Zookeeper session expired. Event: WatchedEvent state:Expired type:None path:null zxid: -1\n\nIn contrast, the previous version (3.9.2) would continuously retry until the network connection was restored, maintaining the session more reliably.\n\nI believe it's a new issue with this change: https://issues.apache.org/jira/browse/ZOOKEEPER-4508\n\n \n\nStep to repro:\n\nOpen VPN.\nStart the application which connects to the Zookeeper server with the VPN.\nDisable VPN for a couple of minutes.\nObserve the application.\nEnable the VPN again.\n3.9.3:\n\"message\" : \"Session 0x0 for server XXX, Closing socket connection. Attempting reconnect except it is a SessionExpiredException or SessionTimeoutException.\",\n \"stackTrace\" : \"o.a.z.ClientCnxn$SessionTimeoutException: Client session timed out, have not heard from server in 5590ms for session id 0x0\n at o.a.z.ClientCnxn$SendThread.run(ClientCnxn.java:1253)\n\n3.9.2: Application will be reconnected successfully.", "branch": "release-3.9.3", "issue_url": "https://issues.apache.org/jira/browse/ZOOKEEPER-4921", "fix_url": "https://github.com/apache/zookeeper/pull/2252", "issue_created": "2025-04-23", "severity": "Critical", "root_cause_type": "Error handling", "bug_complexity": "Easy", "distributed": true, "contains_analysis": false, "analysis_removed": "N/A", "contains_logs": true, "contains_stack_traces": true, "num_artifacts": 0}