[Bug] can't create topic in k8s ipv6. broker #23843
Comments
@zey1996 We don't have tests in the Apache Pulsar project for this. One known detail is that Pulsar sets |
|
I add and I still get exception. It doesn't seem to work. Maybe I did was wrong，or it's a new problem? |
@zey1996 Due to the way how the scripts are structured, it's currently not supported to set You will need to add it to I'll create a separate PR to allow putting In your case you could add |
|
I try to set env PULSAR_EXTRA_OPTS="-Djava.net.preferIPv4Stack=false", but it's not work. I found launch command has two same argument my-release-pulsar-broker-0:/pulsar$ echo $PULSAR_EXTRA_OPTS
-Djava.net.preferIPv4Stack=false
my-release-pulsar-broker-0:/pulsar$ ps -ef|grep java
pulsar 1 0 21 02:07 ? 00:00:24 /opt/jvm/bin/java -Dlog4j.shutdownHookEnabled=false -cp /pulsar/conf:::/pulsar/lib/*: -Dlog4j2.formatMsgNoLookups=true -Dorg.xerial.snappy.use.systemlib=true -Dlog4j.configurationFile=log4j2.yaml -Djute.maxbuffer=10485760 -Djava.net.preferIPv4Stack=true -Dzookeeper.clientTcpKeepAlive=true -Dio.netty.tryReflectionSetAccessible=true --add-opens java.base/java.io=ALL-UNNAMED --add-opens java.base/java.util.zip=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/jdk.internal.misc=ALL-UNNAMED --add-opens java.base/sun.net=ALL-UNNAMED --add-opens java.management/sun.management=ALL-UNNAMED --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED --add-opens java.base/jdk.internal.platform=ALL-UNNAMED -Xms4096m -Xmx4096m -XX:MaxDirectMemorySize=8192m -Dio.netty.leakDetectionLevel=disabled -Dio.netty.recycler.linkCapacity=1024 -XX:+ParallelRefProcEnabled -XX:+UnlockExperimentalVMOptions -XX:+DoEscapeAnalysis -XX:ParallelGCThreads=32 -XX:ConcGCThreads=32 -XX:G1NewSizePercent=50 -XX:+DisableExplicitGC -XX:-ResizePLAB -XX:+ExitOnOutOfMemoryError -Xlog:async -Xlog:gc*,safepoint:/pulsar/logs/pulsar_gc_%p.log:time,uptime,tags:filecount=10,filesize=20M -Djava.net.preferIPv4Stack=false -Dpulsar.log.appender=RoutingAppender -Dpulsar.log.dir=/pulsar/logs -Dpulsar.log.level=info -Dpulsar.log.root.level=info -Dpulsar.log.immediateFlush=false -Dpulsar.routing.appender.default=Console -Dlog4j2.is.webapp=false -Dpulsar.functions.process.container.log.dir=/pulsar/logs -Dpulsar.functions.java.instance.jar=/pulsar/instances/java-instance.jar -Dpulsar.functions.python.instance.file=/pulsar/instances/python-instance/python_instance_main.py -Dpulsar.functions.extra.dependencies.dir=/pulsar/instances/deps -Dpulsar.functions.instance.classpath=/pulsar/conf:::/pulsar/lib/*: -Dpulsar.functions.log.conf=/pulsar/conf/functions_log4j2.xml -Dbookkeeper.metadata.bookie.drivers=org.apache.pulsar.metadata.bookkeeper.PulsarMetadataBookieDriver -Dbookkeeper.metadata.client.drivers=org.apache.pulsar.metadata.bookkeeper.PulsarMetadataClientDriver -Dpulsar.log.file=pulsar-broker.log org.apache.pulsar.PulsarBrokerStarter --broker-conf /pulsar/conf/broker.confI'm learning the start-up process. It may take a while. |
Yes, that is expected. The last parameter "wins". |
I do this. but I can't understand, It looks like it could work. my-release-pulsar-broker-2:/pulsar$ jinfo -sysprops 1|grep IP
java.net.preferIPv4Stack=false
my-release-pulsar-broker-2:/pulsar$ jcmd 1 VM.system_properties|grep IP
java.net.preferIPv4Stack=falseI found |
As you can see, the value is
There is no need to add a switch since the value is |
|
sorry I don't understand. Let me sort it out。 in now I still get exception. |
It is needed in all Pulsar components. It's possible that there are also some other gaps in IPv6 support since we don't have tests as part of CI to ensure that IPv6 is supported. It's up to contributors like you to test and address possible issues. |
Search before asking
Read release policy
Version
k8s with ipv6
imag version:3.3.3
no client, just cli.
Minimal reproduce step
this is my broker deploy yaml file:
What did you expect to see?
I am a newer for pulsar, I just want to run a demo of pulsar cluster with some node.
first. I deploy my pods in k8s cluster. they are look good.
then, I want to create a topic, but I'm failed.
What did you see instead?
in pulsar-admin cli, I got this.
then I found some exception log in broker pod:
It appears that pulsar cannot use ipv6 dns server?
I confirm the dns server in log is working.
Can I run pulsar in ipv6 k8s cluster?
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: