alberttwong commented on PR #11919: URL: https://github.com/apache/nifi/pull/11919#issuecomment-6986168160
@pvillard31 I completed live acceptance testing at b0e73a902c22b4e3e4c478f849945839f46a16c2 and updated the PR description with the matrix, connection-mode guidance, and remaining checks. **Standalone mode** connects NiFi to one Enterprise Software or Redis Cloud database proxy endpoint. Redis routes requests across its backend shards and nodes, so this mode supports sharded, multi-node deployments. **Cluster mode / OSS Cluster API** makes the client discover the slot topology and connect to the relevant node proxies; it can reduce internal forwarding but is not required for sharded proxy access. Official references: [proxy policies](https://redis.io/docs/latest/operate/rs/databases/configure/proxy-policy/), [Cluster API architecture](https://redis.io/docs/latest/operate/rs/clusters/optimize/oss-cluster-api/), and [Cloud clustering](https://redis.io/docs/latest/operate/rc/databases/configuration/clustering/). Software passed 1 node / 1 shard, 1 node / 3 shards, 3 nodes / 1 replicated primary, and 3 nodes / 3 primaries. Newly provisioned Cloud Pro databases with 1 and 2 primary shards also passed, both with TLS and multi-zone replication. These tests used Standalone mode. Software runs verified effective 4x QPF; Cloud readbacks confirmed 4x QPF. **115 selected integration executions passed**, including restricted ACLs without WATCH/MULTI/EXEC, mTLS, missing-EVAL refusals without changing data, planned failover, abrupt primary-node loss, and continuous atomic operations during a one-to-three-shard expansion (7,516 cycles read back, no mutation retries). The external-endpoint harnesses are local artifacts and are not yet committed; the description distinguishes those runs from the committed fixtures. The MOVED/ASK gap remains on the separate Cluster API test path. These proxy tests do not establish multi-node client redirects or global Active-Active compare-and-set. Temporary test resources were deleted. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
