You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iotdb.apache.org by xi...@apache.org on 2022/08/26 09:05:25 UTC
[iotdb] branch xingtanzjr/change_response_wal created (now 11ecb2c319)
This is an automated email from the ASF dual-hosted git repository.
xingtanzjr pushed a change to branch xingtanzjr/change_response_wal
in repository https://gitbox.apache.org/repos/asf/iotdb.git
at 11ecb2c319 change response code to WRITE_PROCESS_REJECT when limitation is triggered by wal size
This branch includes the following new commits:
new 11ecb2c319 change response code to WRITE_PROCESS_REJECT when limitation is triggered by wal size
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
[iotdb] 01/01: change response code to WRITE_PROCESS_REJECT when limitation is triggered by wal size
Posted by xi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
xingtanzjr pushed a commit to branch xingtanzjr/change_response_wal
in repository https://gitbox.apache.org/repos/asf/iotdb.git
commit 11ecb2c319ff053d4613241010265f69de32b588
Author: Jinrui.Zhang <xi...@gmail.com>
AuthorDate: Fri Aug 26 17:05:09 2022 +0800
change response code to WRITE_PROCESS_REJECT when limitation is triggered by wal size
---
.../org/apache/iotdb/consensus/multileader/MultiLeaderServerImpl.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/consensus/src/main/java/org/apache/iotdb/consensus/multileader/MultiLeaderServerImpl.java b/consensus/src/main/java/org/apache/iotdb/consensus/multileader/MultiLeaderServerImpl.java
index 619e9fb32d..0488daf658 100644
--- a/consensus/src/main/java/org/apache/iotdb/consensus/multileader/MultiLeaderServerImpl.java
+++ b/consensus/src/main/java/org/apache/iotdb/consensus/multileader/MultiLeaderServerImpl.java
@@ -127,7 +127,7 @@ public class MultiLeaderServerImpl {
!stateMachineCondition.await(
config.getReplication().getThrottleTimeOutMs(), TimeUnit.MILLISECONDS);
if (timeout) {
- return RpcUtils.getStatus(TSStatusCode.READ_ONLY_SYSTEM_ERROR);
+ return RpcUtils.getStatus(TSStatusCode.WRITE_PROCESS_REJECT);
}
} catch (InterruptedException e) {
logger.error("Failed to throttle down because ", e);