Re: [PR] KAFKA-9914: Fix replication cycle detection [kafka]

2024-04-10 Thread via GitHub


izmal commented on PR #10277:
URL: https://github.com/apache/kafka/pull/10277#issuecomment-2047967071

   I my case reason for replication cycle was:
   `replication.policy.separator = -`
   With another separator works without cycle (e.g '_'). :-)


-- 
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: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] KAFKA-9914: Fix replication cycle detection [kafka]

2024-04-09 Thread via GitHub


izmal commented on PR #10277:
URL: https://github.com/apache/kafka/pull/10277#issuecomment-2045923897

   Hello!
   I got some issue. Aslo I tried add **heartbeats** topic in `topics.exclude` 
and `topics.blacklist` but it isn't help.
   I have two geo cluster. And need use A as backup for B and vice versa.
   
   Replication topics from DC A to DC B with prefix `dc-a-`
   mm2 in DC B:
   ```ini
   # sync kafka topics dc-a -> dc-b
   clusters=dc-a, dc-b-target
   
   # replicated topics -
   replication.policy.separator=-
   
   dc-a.bootstrap.servers=dc-a:9092
   dc-b-target.bootstrap.servers=dc-b:9092
   
   dc-a->dc-b-target.enabled=true
   
   topics.blacklist=heartbeats, dc-b-.*
   topics.exclude=heartbeats, dc-b-.*
   ```
   
   Replication topics from DC B to DC A with prefix `dc-b-`
   mm2 in DC A:
   ```ini
   # sync kafka topics dc-b -> dc-a
   clusters=dc-b, dc-a-target
   
   # replicated topics -
   replication.policy.separator=-
   
   dc-b.bootstrap.servers=dc-b:9092
   dc-a-target.bootstrap.servers=dc-a:9092
   
   dc-b->dc-a-target.enabled=true
   
   topics.blacklist=heartbeats, dc-a-.*
   topics.exclude=heartbeats, dc-a-.*
   ```
   
   For success story i want see topics in DC A:
   ```bash
   first # local topic in DC A
   dc-b-first # topic from DC B
   ```
   
   topics in DC B:
   ```bash
   first # local topic in DC A
   dc-a-first # topic from DC A
   ```
   
   For example result in dc-b (aslo looks like bug -- exclude does not work for 
**heartbeats** via `topics.exclude=dc-b-.*`):
   ```
   root@dc-b:~# /opt/kafka/bin/kafka-topics.sh --bootstrap-server 
localhost:9092 --list | grep heartbeats
   
dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-heartbeats
   dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-heartbeats
   dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-heartbeats
   dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-heartbeats
   dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-heartbeats
   dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-heartbeats
   dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-heartbeats
   dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-dc-a-heartbeats
   dc-a-dc-b-dc-a-dc-b-dc-a-dc-b-heartbeats
   dc-a-dc-b-dc-a-dc-b-dc-a-heartbeats
   dc-a-dc-b-dc-a-dc-b-heartbeats
   dc-a-dc-b-dc-a-heartbeats
   dc-a-dc-b-heartbeats # <- this should not replicated via 
`topics.exclude=dc-b-.*`
   dc-a-heartbeats
   heartbeats
   ```


-- 
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: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org