lifecycle-conductor: check transition processor lag

There may be lag on the transition processor, should throttle the conductor as well. Issue: BB-437
scality · Oct 3, 2023 · 1596051 · 1596051
1 parent c5b4e58
commit 1596051
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 2 deletions.
diff --git a/extensions/lifecycle/conductor/LifecycleConductor.js b/extensions/lifecycle/conductor/LifecycleConductor.js
@@ -747,12 +747,18 @@ class LifecycleConductor {
                 this.lcConfig.bucketTasksTopic,
                 this.lcConfig.bucketProcessor.groupId, 0, next),
 
-            // check that object tasks topic consumer lag is 0
-            objectTasksCheck:
+            // check that object tasks topic consumer lag for expirations is 0
+            objectTasksExpirationCheck:
             next => this._kafkaBacklogMetrics.checkConsumerLag(
                 this.lcConfig.objectTasksTopic,
                 this.lcConfig.objectProcessor.groupId, 0, next),
 
+            // check that object tasks topic consumer lag for transitions is 0
+            objectTasksTransitionCheck:
+                next => this._kafkaBacklogMetrics.checkConsumerLag(
+                    this.lcConfig.objectTasksTopic,
+                    this.lcConfig.transitionProcessor.groupId, 0, next),
+
             // check that data mover topic consumer has progressed
             // beyond the latest lifecycle snapshot of topic offsets,
             // which means everything from the latest lifecycle batch

diff --git a/tests/functional/lifecycle/LifecycleConductor.spec.js b/tests/functional/lifecycle/LifecycleConductor.spec.js
@@ -179,6 +179,9 @@ describe('lifecycle conductor', function lifecycleConductor() {
                 objectProcessor: {
                     groupId: 'b',
                 },
+                transitionProcessor: {
+                    groupId: 'c',
+                },
             };
 
             // make topic unique so that different tests' bootstrap messages don't interfere
@@ -279,6 +282,9 @@ describe('lifecycle conductor', function lifecycleConductor() {
                 objectProcessor: {
                     groupId: 'b',
                 },
+                transitionProcessor: {
+                    groupId: 'c',
+                },
             };
 
             // make topic unique so that different tests' bootstrap messages don't interfere