apache / apache/pulsar-client-cpp
disableReplication in MessageBuilder does not work in PulsarClient C++ and Java
- Lingua principale
- C++
- Stelle
- 71
- Fork
- 90
- Merge medio
- 2h 33m
- PR unite (30g)
- 3
Descrizione
**Describe the bug**
Data is still replicated when disableReplication is enabled
**To Reproduce**
Steps to reproduce the behavior:
1. Setup Geo-Replication with 3 cluster(A,B,C)
2. Set disableReplication = true in MessageBuilder
```
Message msg = MessageBuilder().setContent("repl").disableReplication(true).build();
```
3. Producer create connect in cluster C and send ```Message msg```
```
producer.sendAsync(msg, notifySendMessage);
```
**Actual output is consumer**
1. Cluster A
```
Received message: repl
```
2. Cluster A
```
Received message: repl
```
3. Cluster C
```
Received message: repl
```
**Expected output is**
1. Cluster A
```
```
2. Cluster A
```
```
3. Cluster C
```
Received message: repl
```
Pulsar version: 2.3.0
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by tracing MessageBuilder.disableReplication(true) through the C++ client and the producer.sendAsync path, using the three-cluster geo-replication steps to reproduce the behavior. Done means a message sent from cluster C remains in C and is not received by clusters A or B when replication is disabled.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- cpp, java
- Ambito
- distributed-systems
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100