This is an automated email from the ASF dual-hosted git repository.

tanxinyu pushed a commit to branch rel/1.2
in repository https://gitbox.apache.org/repos/asf/iotdb.git


The following commit(s) were added to refs/heads/rel/1.2 by this push:
     new 14cef78ab42 [To rel/1.2][IOTDB-6085] NullPointerException in readAsync 
when Ratis leader is changing (#10707)
14cef78ab42 is described below

commit 14cef78ab426e05f2fe006f0a76db408f42fc5e8
Author: Xiangpeng Hu <[email protected]>
AuthorDate: Thu Jul 27 21:12:13 2023 +0800

    [To rel/1.2][IOTDB-6085] NullPointerException in readAsync when Ratis 
leader is changing (#10707)
---
 .../org/apache/iotdb/confignode/manager/cq/CQManager.java  | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git 
a/iotdb-core/confignode/src/main/java/org/apache/iotdb/confignode/manager/cq/CQManager.java
 
b/iotdb-core/confignode/src/main/java/org/apache/iotdb/confignode/manager/cq/CQManager.java
index f44c5749655..bbbae4f3b2e 100644
--- 
a/iotdb-core/confignode/src/main/java/org/apache/iotdb/confignode/manager/cq/CQManager.java
+++ 
b/iotdb-core/confignode/src/main/java/org/apache/iotdb/confignode/manager/cq/CQManager.java
@@ -117,6 +117,15 @@ public class CQManager {
   }
 
   public void startCQScheduler() {
+    try {
+      /*
+        TODO: remove this after fixing IOTDB-6085
+        sleep here because IOTDB-6085: NullPointerException in readAsync when 
Ratis leader is changing
+      */
+      Thread.sleep(1000);
+    } catch (InterruptedException e) {
+      Thread.currentThread().interrupt();
+    }
     lock.writeLock().lock();
     try {
       // 1. shutdown previous cq schedule thread pool
@@ -156,6 +165,11 @@ public class CQManager {
           // consensus layer related errors
           LOGGER.warn(
               "Unexpected error happened while fetching cq list: ", 
response.getException());
+          try {
+            Thread.sleep(500);
+          } catch (InterruptedException e) {
+            Thread.currentThread().interrupt();
+          }
         }
       }
 

Reply via email to