graham-macdonald-simplisafe opened a new issue, #478:
URL: https://github.com/apache/pulsar-client-node/issues/478
**Summary**
The ConsumerConfig interface does not expose `replicateSubscriptionState`,
which is needed for geo-replication failover scenarios where subscription
cursor state should be synchronized across clusters.
**Context**
The underlying C++ client supports `replicateSubscriptionStateEnabled` as a
consumer configuration option, and it is exposed in other clients. The Node.js
client wraps the C++ library, so the capability should be available at the
binding layer, it just needs to be surfaced in the ConsumerConfig interface and
passed through to the C++ ConsumerConfiguration.
**Expected API**
```
export interface ConsumerConfig {
// ... existing properties ...
replicateSubscriptionState?: boolean;
}
```
When set to true, the broker synchronizes acknowledgment state for this
subscription across geo-replicated clusters, enabling seamless consumer
failover without reprocessing the backlog.
**Use Case**
When deploying Pulsar with geo-replication across multiple regions for
active-passive consumer failover, standby consumers in the secondary region to
need to have a warm subscription cursor that reflects what the primary region
has already processed. Without `replicateSubscriptionState`, the only options
are reprocessing the full backlog on failover or building custom cursor
synchronization.
--
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]
