[Bug] How do I modify ipv6 support
- 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?


### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor 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