@yroshcha/node-red-contrib-redis-full 1.0.5 → 1.0.6

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to this project are documented in this file.
 
+## 1.0.6 — 2026-08-11
+
+### Fixed
+
+- `redis xreadgroup` now restores its consumer group with `MKSTREAM` when a running consumer receives `NOGROUP`, including a deleted or restarted DLQ stream.
+
 ## 1.0.5 — 2026-08-11
 
 ### Fixed

package/README.md

@@ -45,7 +45,7 @@ For a local archive, use `npm install /path/to/yroshcha-node-red-contrib-redis-f
 
 ## Release status
 
-**`1.0.5` is the current stable release.** See [CHANGELOG.md](CHANGELOG.md) for release notes and compatibility information.
+**`1.0.6` is the current stable release.** See [CHANGELOG.md](CHANGELOG.md) for release notes and compatibility information.
 
 ## Production profile
 
@@ -62,6 +62,7 @@ Safe consumer defaults and important settings:
 - **Max deliveries = 5.** After the limit is exceeded, an entry is atomically moved to `<stream>:dlq` and acknowledged. In Redis Cluster, source and DLQ keys must share a hash tag, for example `orders:{eu}` and `orders:{eu}:dlq`.
 - **Start paused (wait for resume)** makes a consumer create/verify its group without calling `XREADGROUP`. It takes no work until a control-plane `resume` request arrives; use it for controlled pod startup after readiness checks.
 - Startup initialisation retries a failed dedicated connection, `XGROUP CREATE`, and the initial `SUBSCRIBE` up to **five times** with exponential backoff and jitter. A transient Redis/TLS/DNS delay does not permanently stop a new consumer or subscriber.
+- If a consumer group disappears after startup (for example after a Redis restart, `XGROUP DESTROY`, or deleting an empty DLQ stream), `redis xreadgroup` recreates it with `MKSTREAM` and resumes.
 - `redis xautoclaim` limits each manual recovery run through `Run limit` (default 1000), avoiding oversized Node-RED payloads.
 - `redis scan` limits one emitted Node-RED message to **10,000** items by default. It sets `msg.scanTruncated = true` when that safety limit is reached; raise `Result limit` / `msg.maxResults` only after sizing the Node-RED heap for the result.
 - `MAXLEN` in `redis xadd` remains blocked until **Allow unsafe MAXLEN trim** is explicitly confirmed. Trimming can remove a payload still represented in a PEL.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yroshcha/node-red-contrib-redis-full",
-  "version": "1.0.5",
+  "version": "1.0.6",
   "description": "Production-oriented Redis palette for Node-RED: generic commands, Pub/Sub, scans, transactions, and Redis Streams consumer groups.",
   "keywords": ["node-red", "redis", "redis-streams", "pubsub", "xadd", "xreadgroup", "ioredis"],
   "license": "MIT",

package/redis.js

@@ -173,6 +173,10 @@ module.exports = function (RED) {
     return obj;
   }
 
+  function isNoGroupError(err) {
+    return String(err && err.message ? err.message : err).includes('NOGROUP');
+  }
+
   // ---------------------------------------------------------------------
   // yroshcha-redis-command — БУДЬ-ЯКА команда Redis через ioredis .call().
   // "block" форсує окреме з'єднання (для BLPOP/BRPOP/WAIT тощо).
@@ -962,6 +966,22 @@ module.exports = function (RED) {
         } catch (err) {
           if (stopped) break;
 
+          // A Redis restart, a manual XGROUP DESTROY, or deletion of an empty
+          // DLQ stream can remove the group after this node has started.
+          // Recreate it before backing off; ensureGroup handles a concurrent
+          // creator through BUSYGROUP and is safe to call repeatedly.
+          if (isNoGroupError(err)) {
+            try {
+              await ensureGroup(blockingClient);
+              currentBackoffMs = node.initialBackoffMs;
+              node.status({ fill: 'yellow', shape: 'ring', text: 'consumer group restored' });
+              node.warn(`Redis stream consumer group restored: ${node.group}@${node.streamKey}`);
+              continue;
+            } catch (restoreErr) {
+              err = restoreErr;
+            }
+          }
+
           const jitter = Math.random() * currentBackoffMs * 0.3; // до +30%
           const delay = Math.min(currentBackoffMs, node.maxBackoffMs) + jitter;