Repository navigation
|
Environment Apache Pulsar: 4.2.5 Deployment: Docker Compose Mode: Standalone (bin/pulsar standalone) Storage: Persistent Docker volume mounted at /pulsar/data Operating system: macOS with Docker Desktop Network: Docker bridge network Problem description I'm running Apache Pulsar 4.2.5 in standalone mode using Docker Compose. After restarting the container or changing its network configuration, BookKeeper attempts to connect to a stale container IP address (172.19.0.3:46565). This causes the managed ledger for persistent://public/functions/__change_events to fail to open and recover. The container can start successfully when I explicitly assign the old IP address 172.19.0.3, but I would prefer not to hardcode a container IP in Docker Compose. pulsar: |
Replies: 1 comment 1 reply
|
Pulsar standalone has been tied to the IP address in the past due to not using BK cookie IDs. In master / branch-5.0, this was addressed by #25694 and #26790. Unfortunately it is not possible to convert data from a previous installation to make it decoupled from the IP addresses. When upgrading to Pulsar 5.x when existing data exists, it will take the legacy path which is tied to the IP addresses. Could you start with scratch with |
Pulsar standalone has been tied to the IP address in the past due to not using BK cookie IDs. In master / branch-5.0, this was addressed by #25694 and #26790. Unfortunately it is not possible to convert data from a previous installation to make it decoupled from the IP addresses. When upgrading to Pulsar 5.x when existing data exists, it will take the legacy path which is tied to the IP addresses.
Could you start with scratch with
apachepulsar/pulsar:5.0.0image?