From 4dac2561cc29800fc43471c8d83a52b3f277c493 Mon Sep 17 00:00:00 2001 From: Daniel Silva Date: Tue, 4 Jun 2024 18:46:29 +0200 Subject: [PATCH] adjust comment --- sqlitecluster/SQLiteNode.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sqlitecluster/SQLiteNode.cpp b/sqlitecluster/SQLiteNode.cpp index 316e97f4c..fd65588b8 100644 --- a/sqlitecluster/SQLiteNode.cpp +++ b/sqlitecluster/SQLiteNode.cpp @@ -1719,7 +1719,7 @@ void SQLiteNode::_onMESSAGE(SQLitePeer* peer, const SData& message) { // If the server is strugling and falling behind on replication, we might have too many threads // causing a resource exhaustion. If that happens, all the transations that are already threaded // and waiting for the transaction that failed will be stuck in an infinite loop. To prevent that - // we're cancelling all threads that would need to wait on the transaction that is failing. + // we're cancelling all threads that would need to wait on the transaction failed to be threaded. uint64_t cancelAfter = message.calcU64("NewCount") - 1; _localCommitNotifier.cancel(cancelAfter); _leaderCommitNotifier.cancel(cancelAfter);