jason810496 commented on code in PR #68938:
URL: https://github.com/apache/airflow/pull/68938#discussion_r3471490785
##########
airflow-core/docs/authoring-and-scheduling/language-sdks/java.rst:
##########
@@ -669,6 +687,44 @@ All ``kwargs`` in the ``coordinators`` config entry are
passed to the
- Seconds to wait for the JVM subprocess to connect after launch.
Increase this if your
JVM startup is slow (e.g. on constrained hardware or with a large
classpath).
+.. note::
+
+ The ``[sdk]`` configuration is read at startup, so changes to
``coordinators`` or
+ ``queue_to_coordinator`` (for example adding ``jvm_args``) only take effect
after you restart the
+ scheduler (or ``airflow standalone``). A rebuilt bundle JAR, by contrast, is
picked up on the next
+ task launch without a restart, because a fresh JVM is spawned per task
instance.
+
+.. _java-sdk/macos:
+
+macOS setup
+-----------
+
+Two extra coordinator settings are needed when running tasks on macOS:
+
+* **Force the JVM onto IPv4.** The coordinator verifies that the task JVM owns
its callback socket. On
+ macOS a dual-stack JVM reports its local address in the IPv4-compatible form
(``::127.0.0.1``),
Review Comment:
The root cause is that the coordinator will get `::127.0.0.1` form instead
of `::ffff:127.0.0.1` for macOS platform. I prefer to fix on coordinator side
in the following PR:
- https://github.com/apache/airflow/pull/68960
I will remove the `-Djava.net.preferIPv4Stack=true` workaround part once
#68960 get merged.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
