apache / apache/pulsar

[Bug] How do I modify ipv6 support

Open
#21,518 0 comments 0 reactions 0 assignees View on GitHub
type/bug
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Version

3.0.1

### Minimal reproduce step

vi bin/pulsar
OPTS="$OPTS -Djute.maxbuffer=10485760 -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Stack=true"

vi pulsar-admin-common.sh
OPTS="$OPTS -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Stack=true"
vi conf/broker
bindAddress=0.0.0.0
advertisedAddress=[cdce:16459:51a3::968b]

### What did you expect to see?

broker nodes are started and can send and consume messages as normal

### What did you see instead?

![image](https://github.com/apache/pulsar/assets/16098391/adfadf8b-b831-4a57-85fb-f8d4ad219010)
![image](https://github.com/apache/pulsar/assets/16098391/7fee814f-f17f-4e83-83bc-8c3d1b5bec67)

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the IPv6 JVM options in bin/pulsar and pulsar-admin-common.sh, then compare the broker settings in conf/broker, especially bindAddress and advertisedAddress. Reproduce the startup and messaging behavior on Pulsar 3.0.1 with the shown IPv6 address. Done means broker nodes start successfully and can send and consume messages normally.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, shell
Domain
distributed-systems, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.