search

testcontainers / testcontainers-java

Testcontainers is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.
https://testcontainers.org
MIT License
8.01k stars 1.65k forks source link

[Bug]: Cannot create a RedpandaContainer with a custom listener without a network #9368

Open YanivKunda opened 1 week ago

YanivKunda commented 1 week ago

Module

Redpanda

Testcontainers version

1.20.2

Using the latest Testcontainers version?

Yes

Host OS

MacOS

Host Arch

ARM

Docker version

Client: Version: 27.1.1 API version: 1.46 Go version: go1.21.12 Git commit: 6312585 Built: Tue Jul 23 19:54:12 2024 OS/Arch: darwin/arm64 Context: desktop-linux

Server: Docker Desktop 4.33.0 (160616) Engine: Version: 27.1.1 API version: 1.46 (minimum version 1.24) Go version: go1.21.12 Git commit: cc13f95 Built: Tue Jul 23 19:57:14 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.7.19 GitCommit: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41 runc: Version: 1.7.19 GitCommit: v1.1.13-0-g58aa920 docker-init: Version: 0.19.0 GitCommit: de40ad0

What happened?

Following https://github.com/testcontainers/testcontainers-java/pull/9247, trying to start a RedpandaContainer with a custom listener _but without a network results in the container failing with the following error: [shard 0] redpanda::main - application.cc:255 - Failure during startup: std::__1::system_error (error C-Ares:4, my-kafka: Not found)

The following test I added to RedpandaContainerTest exhibits the problem:

    @Test
    public void testUsageWithListenerWithoutNetwork() throws Exception {
        try (RedpandaContainer container = new RedpandaContainer(REDPANDA_DOCKER_IMAGE)
            .withListener("my-kafka:29092")
        ) {
            container.start();
            testKafkaFunctionality(container.getBootstrapServers());
        }
    }

The problem doesn't happen when using the now-deprecated .withListener() overload like this:

            .withListener(() -> "my-kafka:29092")

This makes the resulting redpanda.yaml file have the following under redpanda.kafka_api:

    - address: 0.0.0.0
      name: my-kafka
      port: 29092
      authentication_method: none

Also, the problem doesn't happen when using the new overload like this:

            .withListener("0.0.0.0:29092", () -> "my-kafka:29092")

but this results in the names of both the listener and advertised listener being 0.0.0.0 (which I'm not sure is a problem).

Relevant log output

yyyy-mm-dd hh:mi:ss + /usr/local/bin/supervisord -d yyyy-mm-dd hh:mi:ss + '[' '' = true ']' yyyy-mm-dd hh:mi:ss + exec /usr/bin/rpk redpanda start --mode=dev-container --smp=1 --memory=1G yyyy-mm-dd hh:mi:ss WARNING: This is a setup for development purposes only; in this mode your clusters may run unrealistically fast and data can be corrupted any time your computer shuts down uncleanly. yyyy-mm-dd hh:mi:ss INFO redpanda::main - application.cc:213 - Redpanda v22.2.1 - ec6bb903d310de2d99398671b3151df549203a23 yyyy-mm-dd hh:mi:ss We'd love to hear about your experience with redpanda: yyyy-mm-dd hh:mi:ss https://redpanda.com/feedback yyyy-mm-dd hh:mi:ss Starting redpanda... yyyy-mm-dd hh:mi:ss Running: yyyy-mm-dd hh:mi:ss HOSTNAME=a67a76e3159f EDITOR=vi PWD=/ HOME=/root SHLVL=0 PATH=/opt/redpanda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /opt/redpanda/bin/redpanda redpanda --redpanda-cfg /etc/redpanda/redpanda.yaml --lock-memory=false --overprovisioned --smp=1 --memory=1G --reserve-memory=0M --unsafe-bypass-fsync=true yyyy-mm-dd hh:mi:ss yyyy-mm-dd hh:mi:ss yyyy-mm-dd hh:mi:ss Welcome to the Redpanda community! yyyy-mm-dd hh:mi:ss yyyy-mm-dd hh:mi:ss Documentation: https://docs.redpanda.com - Product documentation site yyyy-mm-dd hh:mi:ss GitHub Discussion: https://github.com/redpanda-data/redpanda/discussions - Longer, more involved discussions yyyy-mm-dd hh:mi:ss GitHub Issues: https://github.com/redpanda-data/redpanda/issues - Report and track issues with the codebase yyyy-mm-dd hh:mi:ss Support: https://support.redpanda.com - Contact the support team privately yyyy-mm-dd hh:mi:ss Product Feedback: https://redpanda.com/feedback - Let us know how we can improve your experience yyyy-mm-dd hh:mi:ss Slack: https://redpanda.com/slack - Chat about all things Redpanda. Join the conversation! yyyy-mm-dd hh:mi:ss Twitter: https://twitter.com/redpandadata - All the latest Redpanda news! yyyy-mm-dd hh:mi:ss yyyy-mm-dd hh:mi:ss yyyy-mm-dd hh:mi:ss INFO redpanda::main - application.cc:221 - kernel=6.10.0-linuxkit, nodename=a67a76e3159f, machine=aarch64 yyyy-mm-dd hh:mi:ss WARN yyyy-mm-dd hh:mi:ss,sss [shard 0] seastar - Creation of perf_event based stall detector failed, falling back to posix timer: std::1::system_error (error system:13, perf_event_open() failed: Permission denied) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] seastar - Created fair group io-queue-0, capacity rate 2147483:2147483, limit 12582912, rate 16777216 (factor 1), threshold 2000 yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] seastar - Created io group dev(0), length limit 4194304:4194304, rate 2147483647:2147483647 yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] seastar - Created io queue dev(0) capacities: 512:2000/2000 1024:3000/3000 2048:5000/5000 4096:9000/9000 8192:17000/17000 16384:33000/33000 32768:65000/65000 65536:129000/129000 131072:257000/257000 yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:151 - System resources: { cpus: 1, available memory: 1024.000MiB, reserved memory: 0.000bytes} yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:159 - File handle limit: 1048576/1048576 yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] cluster - config_manager.cc:424 - Can't load config cache: std::1::__fs::filesystem::filesystem_error (error system:2, filesystem error: open failed: No such file or directory ["/var/lib/redpanda/data/config_cache.yaml"]) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:463 - Cluster configuration properties: yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:464 - (use rpk cluster config edit to change) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.abort_index_segment_size:50000 - Capacity (in number of txns) of an abort index segment yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.abort_timed_out_transactions_interval_ms:10000 - How often look for the inactive transactions and abort them yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.admin_api_require_auth:0 - Whether admin API clients must provide HTTP Basic authentication headers yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.aggregate_metrics:0 - Enable aggregations of metrics returned by the prometheus '/metrics' endpoint. Metric aggregation is performed by summing the values of samples by labels. Aggregations are performed where it makes sense by the shard and/or partition labels. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.alter_topic_cfg_timeout_ms:5000 - Time to wait for entries replication in controller log when executing alter configuration requst yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.append_chunk_size:16384 - Size of direct write operations to disk in bytes yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.auto_create_topics_enabled:1 - Allow topic auto creation yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_access_key:{nullopt} - AWS access key yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_api_endpoint:{nullopt}- Optional API endpoint yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_api_endpoint_port:443 - TLS port override yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_bucket:{nullopt} - AWS bucket that should be used to store data yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_cache_check_interval:30000 - Timeout to check if cache eviction should be triggered yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_cache_size:21474836480- Max size of archival cache yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_credentials_source:config_file - The source of credentials to connect to cloud services yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_disable_tls:0 - Disable TLS for all S3 connections yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_enable_remote_read:0 - Enable remote read for all topics yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_enable_remote_write:0 - Enable remote write for all topics yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_enabled:0 - Enable archival storage yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_initial_backoff_ms:100- Initial backoff time for exponetial backoff algorithm (ms) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_manifest_upload_timeout_ms:10000 - Manifest upload timeout (ms) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_max_connection_idle_time_ms:5000 - Max https connection idle time (ms) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_max_connections:20 - Max number of simultaneous connections to S3 per shard (includes connections used for both uploads and downloads) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_metadata_sync_timeout_ms:10000 - Timeout for SI metadata synchronization yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_readreplica_manifest_sync_timeout_ms:30000 - Timeout to check if new data is available for partition in S3 for read replica yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_reconciliation_interval_ms:1000 - Interval at which the archival service runs reconciliation (ms) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_region:{nullopt} - AWS region that houses the bucket used for storage yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_secret_key:{nullopt} - AWS secret key yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_segment_max_upload_interval_sec:{nullopt} - Time that segment can be kept locally without uploading it to the remote storage (sec) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_segment_upload_timeout_ms:30000 - Log segment upload timeout (ms) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_trust_file:{nullopt} - Path to certificate that should be used to validate server certificate during TLS handshake yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_upload_ctrl_d_coeff:0 - derivative coefficient for upload PID controller. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_upload_ctrl_max_shares:1000 - maximum number of IO and CPU shares that archival upload can use yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_upload_ctrl_min_shares:100 - minimum number of IO and CPU shares that archival upload can use yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_upload_ctrl_p_coeff:-2- proportional coefficient for upload PID controller yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_upload_ctrl_update_interval_ms:60000 - yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_upload_loop_initial_backoff_ms:100 - Initial backoff interval when there is nothing to upload for a partition (ms) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_upload_loop_max_backoff_ms:10000 - Max backoff interval when there is nothing to upload for a partition (ms) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cluster_id:{nullopt} - Cluster identifier yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.compacted_log_segment_size:268435456- How large in bytes should each compacted log segment be (default 256MiB) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.compaction_ctrl_backlog_size:{nullopt} - target backlog size for compaction controller. if not set compaction target compaction backlog would be equal to yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.compaction_ctrl_d_coeff:0.2 - derivative coefficient for compaction PID controller. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.compaction_ctrl_i_coeff:0 - integral coefficient for compaction PID controller. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.compaction_ctrl_max_shares:1000 - maximum number of IO and CPU shares that compaction process can use yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.compaction_ctrl_min_shares:10 - minimum number of IO and CPU shares that compaction process can use yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.compaction_ctrl_p_coeff:-12.5 - proportional coefficient for compaction PID controller. This has to be negative since compaction backlog should decrease when number of compaction shares increases yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.compaction_ctrl_update_interval_ms:30000 - yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.controller_backend_housekeeping_interval_ms:1000 - Interval between iterations of controller backend housekeeping loop yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.coproc_max_batch_size:32768 - Maximum amount of bytes to read from one topic read yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.coproc_max_inflight_bytes:10485760 - Maximum amountt of inflight bytes when sending data to wasm engine yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.coproc_max_ingest_bytes:655360 - Maximum amount of data to hold from input logs in memory yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.coproc_offset_flush_interval_ms:300000 - Interval for which all coprocessor offsets are flushed to disk yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.create_topic_timeout_ms:2000 - Timeout (ms) to wait for new topic creation yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.default_num_windows:10 - Default number of quota tracking windows yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.default_topic_partitions:1 - Default number of partitions per topic yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.default_topic_replications:1 - Default replication factor for new topics yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.default_window_sec:1000 - Default quota tracking window size in milliseconds yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.delete_retention_ms:604800000 - delete segments older than this - default 1 week yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.disable_batch_cache:0 - Disable batch cache in log manager yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.disable_metrics:0 - Disable registering metrics exposed on the internal metrics endpoint (/metrics) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.disable_public_metrics:0 - Disable registering metrics exposed on the public metrics endpoint (/public_metrics) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.election_timeout_ms:1500 - Election timeout expressed in milliseconds yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_admin_api: - yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_auto_rebalance_on_node_add:0 - Enable automatic partition rebalancing when new nodes are added yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_coproc:0 - Enable coprocessing mode yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_idempotence:1 - Enable idempotent producer yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_leader_balancer:1 - Enable automatic leadership rebalancing yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_metrics_reporter:1 - Enable cluster metrics reporter yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_pid_file:1 - Enable pid file. You probably don't want to change this. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_rack_awareness:0 - Enables rack-aware replica assignment yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_sasl:0 - Enable SASL authentication for Kafka connections, authorization is required. see also kafka_enable_authorization yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_transactions:0 - Enable transactions yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.features_auto_enable:1 - Whether new feature flags may auto-activate after upgrades (true) or must wait for manual activation via the admin API (false) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.fetch_max_bytes:57671680 - Maximum number of bytes returned in fetch request yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.fetch_reads_debounce_timeout:1 - Time to wait for next read in fetch request when requested min bytes wasn't reached yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.fetch_session_eviction_timeout_ms:60000 - Minimum time before which unused session will get evicted from sessions. Maximum time after which inactive session will be deleted is two time given configuration valuecache yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.full_raft_configuration_recovery_pattern:{} - Recover raft configuration on start for NTPs matching pattern yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.group_initial_rebalance_delay:3000 - Extra delay (ms) added to rebalance phase to wait for new members yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.group_max_session_timeout_ms:300000 - The maximum allowed session timeout for registered consumers. Longer timeouts give consumers more time to process messages in between heartbeats at the cost of a longer time to detect failures. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.group_min_session_timeout_ms:6000 - The minimum allowed session timeout for registered consumers. Shorter timeouts result in quicker failure detection at the cost of more frequent consumer heartbeating, which can overwhelm broker resources. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.group_new_member_join_timeout:30000 - Timeout for new member joins yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.group_topic_partitions:16 - Number of partitions in the internal group membership topic yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.health_manager_tick_interval:180000 - How often the health manager runs yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.health_monitor_max_metadata_age:10000- Max age of metadata cached in the health monitor of non controller node yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.health_monitor_tick_interval:10000 - How often health monitor refresh cluster state yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.id_allocator_batch_size:1000 - Id allocator allocates messages in batches (each batch is a one log record) and then serves requests from memory without touching the log until the batch is exhausted. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.id_allocator_log_capacity:100 - Capacity of the id_allocator log in number of messages. Once it reached id_allocator_stm should compact the log. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.id_allocator_replication:1 - Replication factor for an id allocator topic yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.internal_topic_replication_factor:3 - Target replication factor for internal topics yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.join_retry_timeout_ms:5000 - Time between cluster join retries in milliseconds yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_connection_rate_limit:{nullopt}- Maximum connections per second for one core yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_connection_rate_limit_overrides:{} - Overrides for specific ips for maximum connections per second for one core yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_connections_max:{nullopt} - Maximum number of Kafka client connections per broker yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_connections_max_overrides:{} - Per-IP overrides of kafka connection count limit, list of : strings yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_connections_max_per_ip:{nullopt} - Maximum number of Kafka client connections from each IP address, per broker yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_enable_authorization:{nullopt}- Enable authorization for Kafka connections. Values:- nil: Ignored. Authorization is enabled with enable_sasl: true; true: authorization is required; false: authorization is disabled. See also: enable_sasl and kafka_api[].authentication_method yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_group_recovery_timeout_ms:30000- Kafka group recovery timeout expressed in milliseconds yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_max_bytes_per_fetch:67108864 - Limit fetch responses to this many bytes, even if total of partition bytes limits is higher yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_mtls_principal_mapping_rules:{nullopt} - Principal Mapping Rules for mTLS Authentication on the Kafka API yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_depth_alpha:0.8 - Smoothing factor for kafka queue depth control depth tracking. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_depth_update_ms:7000 - Update frequency for kafka queue depth control. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_enable:0 - Enable kafka queue depth control. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_idle_depth:10 - Queue depth when idleness is detected in kafka queue depth control. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_latency_alpha:0.002 - Smoothing parameter for kafka queue depth control latency tracking. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_max_depth:100 - Maximum queue depth used in kafka queue depth control. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_max_latency_ms:80 - Max latency threshold for kafka queue depth control depth tracking. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_min_depth:1 - Minimum queue depth used in kafka queue depth control. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_window_count:12 - Number of windows used in kafka queue depth control latency tracking. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_qdc_window_size_ms:1500 - Window size for kafka queue depth control latency tracking. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_rpc_server_stream_recv_buf:{nullopt} - Userspace receive buffer max size in bytes yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_rpc_server_tcp_recv_buf:{nullopt} - Kafka server TCP receive buffer size in bytes. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_rpc_server_tcp_send_buf:{nullopt} - Kafka server TCP transmit buffer size in bytes. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kvstore_flush_interval:10 - Key-value store flush interval (ms) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kvstore_max_segment_size:16777216 - Key-value maximum segment size (bytes) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.leader_balancer_idle_timeout:120000 - Leadership rebalancing idle timeout yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.leader_balancer_mute_timeout:300000 - Leadership rebalancing mute timeout yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.leader_balancer_transfer_limit_per_shard:512 - Per shard limit for in progress leadership transfers yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.log_cleanup_policy:delete - Default topic cleanup policy yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.log_compaction_interval_ms:10000 - How often do we trigger background compaction yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.log_compression_type:producer - Default topic compression type yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.log_message_timestamp_type:CreateTime- Default topic messages timestamp type yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.log_segment_size:1073741824 - How large in bytes should each log segment be (default 1G) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.max_compacted_log_segment_size:5368709120 - Max compacted segment size after consolidation yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.max_kafka_throttle_delay_ms:60000 - Fail-safe maximum throttle delay on kafka requests yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.max_version: - yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.members_backend_retry_ms:5000 - Time between members backend reconciliation loop retries yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.metadata_dissemination_interval_ms:3000 - Interaval for metadata dissemination batching yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.metadata_dissemination_retries:30 - Number of attempts of looking up a topic's meta data like shard before failing a request yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.metadata_dissemination_retry_delay_ms:320 - Delay before retry a topic lookup in a shard or other meta tables yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.metadata_status_wait_timeout_ms:2000- Maximum time to wait in metadata request for cluster health to be refreshed yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.metrics_reporter_report_interval:86400000 - cluster metrics reporter report interval yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.metrics_reporter_tick_interval:60000- Cluster metrics reporter tick interval yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.metrics_reporter_url:https://m.rp.vectorized.io/v2 - cluster metrics reporter url yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.min_version: - yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.node_management_operation_timeout_ms:5000 - Timeout for executing node management operations yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.partition_autobalancing_max_disk_usage_percent:80 - Disk usage threshold that triggers moving partitions from the node yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.partition_autobalancing_mode:node_add- Partition autobalancing mode yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.partition_autobalancing_movement_batch_size_bytes:5368709120 - Total size of partitions that autobalancer is going to move in one batch yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.partition_autobalancing_node_availability_timeout_sec:900000 - Node unavailability timeout that triggers moving partitions from the node yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.partition_autobalancing_tick_interval_ms:30000 - Partition autobalancer tick interval yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.quota_manager_gc_sec:30000 - Quota manager GC frequency in milliseconds yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_heartbeat_disconnect_failures:3- After how many failed heartbeats to forcibly close an unresponsive TCP connection. Set to 0 to disable force disconnection. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_heartbeat_interval_ms:150 - Milliseconds for raft leader heartbeats yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_heartbeat_timeout_ms:3000 - raft heartbeat RPC timeout yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_io_timeout_ms:10000 - Raft I/O timeout yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_learner_recovery_rate:104857600- Raft learner recovery rate limit in bytes per sec yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_max_concurrent_append_requests_per_follower:16 - Maximum number of concurrent append entries requests sent by leader to one follower yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_max_recovery_memory:{nullopt} - Max memory that can be used for reads in raft recovery process by default 15% of total memory yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_recovery_default_read_size:524288 - default size of read issued during raft follower recovery yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_replicate_batch_window_size:1048576 - Max size of requests cached for replication yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_smp_max_non_local_requests:{nullopt} - Maximum number of x-core requests pending in Raft seastar::smp group. (for more details look at seastar::smp_service_group documentation) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_timeout_now_timeout_ms:1000 - Timeout for a timeout now request yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.raft_transfer_leader_recovery_timeout_ms:10000 - Timeout waiting for follower recovery when transferring leadership yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.readers_cache_eviction_timeout_ms:30000 - Duration after which inactive readers will be evicted from cache yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.reclaim_batch_cache_min_free:67108864- Free memory limit that will be kept by batch cache background reclaimer yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.reclaim_growth_window:3000 - Length of time in which reclaim sizes grow yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.reclaim_max_size:4194304 - Maximum batch cache reclaim size yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.reclaim_min_size:131072 - Minimum batch cache reclaim size yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.reclaim_stable_window:10000 - Length of time above which growth is reset yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.recovery_append_timeout_ms:5000 - Timeout for append entries requests issued while updating stale follower yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.release_cache_on_segment_roll:0 - Free cache when segments roll yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.replicate_append_timeout_ms:3000 - Timeout for append entries requests issued while replicating entries yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.retention_bytes:{nullopt} - Default max bytes per partition on disk before triggering a compaction yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.rm_sync_timeout_ms:10000 - Time to wait state catch up before rejecting a request yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.rm_violation_recovery_policy:crash - Describes how to recover from an invariant violation happened on the partition level yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.rpc_server_listen_backlog:{nullopt} - TCP connection queue length for Kafka server and internal RPC server yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.rpc_server_tcp_recv_buf:{nullopt} - Internal RPC TCP receive buffer size in bytes. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.rpc_server_tcp_send_buf:{nullopt} - Internal RPC TCP transmit buffer size in bytes. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.seed_server_meta_topic_partitions: - yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.segment_appender_flush_timeout_ms:1000 - Maximum delay until buffered data is written yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.segment_fallocation_step:33554432 - Size for segments fallocation yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.seq_table_min_size:1000 - Minimum size of the seq table non affected by compaction yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.storage_compaction_index_memory:134217728 - Maximum number of bytes that may be used on each shard by compactionindex writers yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.storage_max_concurrent_replay:1024 - Maximum number of partitions' logs that will be replayed concurrently at startup, or flushed concurrently on shutdown. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.storage_min_free_bytes:5368709120 - Threshold of minimum bytes free space before rejecting producers. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.storage_read_buffer_size:131072 - Size of each read buffer (one per in-flight read, per log segment) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.storage_read_readahead_count:10 - How many additional reads to issue ahead of current read location yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.storage_space_alert_free_threshold_bytes:0 - Threshold of minimim bytes free space before setting storage space alert yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.storage_space_alert_free_threshold_percent:5 - Threshold of minimim percent free space before setting storage space alert yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.storage_target_replay_bytes:10737418240 - Target bytes to replay from disk on startup after clean shutdown: controls frequency of snapshots and checkpoints yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.superusers:{} - List of superuser usernames yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.target_quota_byte_rate:2147483648 - Target quota byte rate (bytes per second) - 2GB default yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.tm_sync_timeout_ms:10000 - Time to wait state catch up before rejecting a request yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.tm_violation_recovery_policy:crash - Describes how to recover from an invariant violation happened on the transaction coordinator level yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.topic_fds_per_partition:{5} - Required file handles per partition when creating topics yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.topic_memory_per_partition:{1048576}- Required memory per partition when creating topics yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.topic_partitions_per_shard:7000 - Maximum number of partitions which may be allocated to one shard (CPU core) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.topic_partitions_reserve_shard0:2 - Reserved partition slots on shard (CPU core) 0 on each node. If this is >= topic_partitions_per_core, no data partitions will be scheduled on shard 0 yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.transaction_coordinator_cleanup_policy:delete - Cleanup policy for a transaction coordinator topic yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.transaction_coordinator_delete_retention_ms:604800000 - delete segments older than this - default 1 week yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.transaction_coordinator_log_segment_size:1073741824 - How large in bytes should each log segment be (default 1G) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.transaction_coordinator_replication:1- Replication factor for a transaction coordinator topic yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.transactional_id_expiration_ms:604800000 - Producer ids are expired once this time has elapsed after the last write with the given producer id. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.tx_timeout_delay_ms:1000 - Delay before scheduling next check for timed out transactions yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.use_scheduling_groups: - yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.wait_for_leader_timeout_ms:5000 - Timeout (ms) to wait for leadership in metadata cache yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.zstd_decompress_workspace_bytes:8388608 - Size of the zstd decompression workspace yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:467 - Node configuration properties: yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:468 - (use rpk config set <cfg> <value> to change) yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.admin:{{:{host: 0.0.0.0, port: 9644}}} - Address and port of admin server yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.admin_api_doc_dir:/usr/share/redpanda/admin-api-doc - Admin API doc directory yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.admin_api_tls:{} - TLS configuration for admin HTTP server yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.advertised_kafka_api:{{external:{host: localhost, port: 54738}}, {internal:{host: 127.0.0.1, port: 9093}}, {kafka:{host: kafka, port: 29092}}} - Address of Kafka API published to the clients yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.advertised_rpc_api:{nullopt} - Address of RPC endpoint published to other cluster members yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.cloud_storage_cache_directory:{nullopt} - Directory for archival cache. Should be present when cloud_storage_enabled is present yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.coproc_supervisor_server:{host: 127.0.0.1, port: 43189} - IpAddress and port for supervisor service yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.dashboard_dir: - yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.data_directory:{data_directory="/var/lib/redpanda/data"} - Place where redpanda will keep the data yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.developer_mode:1 - Skips most of the checks performed at startup, not recomended for production use yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.enable_central_config: - yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_api:{{external:{host: 0.0.0.0, port: 9092}:{none}}, {internal:{host: 0.0.0.0, port: 9093}:{none}}, {kafka:{host: kafka, port: 29092}:{none}}} - Address and port of an interface to listen for Kafka API requests yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.kafka_api_tls:{} - TLS configuration for Kafka API endpoint yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.node_id:{0} - Unique id identifying a node in the cluster yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.rack:{nullopt} - Rack identifier yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.rpc_server:{host: 127.0.0.1, port: 33145} - IpAddress and port for RPC server yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.rpc_server_tls:{ enabled: 0 key/cert files: {nullopt} ca file: {nullopt} client_auth_required: 0 } - TLS configuration for RPC server yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - redpanda.seed_servers:{} - List of the seed servers used to join current cluster. If the seed_server list is empty the node will be a cluster root and it will form a new cluster yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy.advertised_pandaproxy_api:{} - Rest API address and port to publish to client yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy.api_doc_dir:/usr/share/redpanda/proxy-api-doc - API doc directory yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy.consumer_instance_timeout_ms:300000- How long to wait for an idle consumer before removing it yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy.pandaproxy_api:{{proxy-internal:{host: 0.0.0.0, port: 8082}}} - Rest API listen address and port yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy.pandaproxy_api_tls:{} - TLS configuration for Pandaproxy api yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.broker_tls:{ enabled: 0 key/cert files: {nullopt} ca file: {nullopt} client_auth_required: 0 } - TLS configuration for the brokers yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.brokers:{{host: localhost, port: 9093}} - List of address and port of the brokers yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.consumer_heartbeat_interval_ms:500 - Interval (in milliseconds) for consumer heartbeats yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.consumer_rebalance_timeout_ms:2000 - Timeout (in milliseconds) for consumer rebalance yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.consumer_request_max_bytes:1048576 - Max bytes to fetch per request yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.consumer_request_timeout_ms:100 - Interval (in milliseconds) for consumer request timeout yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.consumer_session_timeout_ms:300000 - Timeout (in milliseconds) for consumer session yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.produce_batch_delay_ms:100 - Delay (in milliseconds) to wait before sending batch yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.produce_batch_record_count:1000 - Number of records to batch before sending to broker yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.produce_batch_size_bytes:1048576 - Number of bytes to batch before sending to broker yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.retries:5 - Number of times to retry a request to a broker yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.retry_base_backoff_ms:100 - Delay (in milliseconds) for initial retry backoff yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.sasl_mechanism: - The SASL mechanism to use when connecting yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.scram_password: - Password to use for SCRAM authentication mechanisms yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - pandaproxy_client.scram_username: - Username to use for SCRAM authentication mechanisms yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry.api_doc_dir:/usr/share/redpanda/proxy-api-doc - API doc directory yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry.schema_registry_api:{{main:{host: 0.0.0.0, port: 8081}}} - Schema Registry API listen address and port yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry.schema_registry_api_tls:{} - TLS configuration for Schema Registry API yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry.schema_registry_replication_factor:{nullopt} - Replication factor for internal _schemas topic. If unset, defaults to default_topic_replication yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.broker_tls:{ enabled: 0 key/cert files: {nullopt} ca file: {nullopt} client_auth_required: 0 } - TLS configuration for the brokers yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.brokers:{{host: localhost, port: 9093}} - List of address and port of the brokers yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.consumer_heartbeat_interval_ms:500 - Interval (in milliseconds) for consumer heartbeats yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.consumer_rebalance_timeout_ms:2000 - Timeout (in milliseconds) for consumer rebalance yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.consumer_request_max_bytes:1048576 - Max bytes to fetch per request yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.consumer_request_timeout_ms:100 - Interval (in milliseconds) for consumer request timeout yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.consumer_session_timeout_ms:10000 - Timeout (in milliseconds) for consumer session yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.produce_batch_delay_ms:100 - Delay (in milliseconds) to wait before sending batch yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.produce_batch_record_count:1000 - Number of records to batch before sending to broker yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.produce_batch_size_bytes:1048576 - Number of bytes to batch before sending to broker yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.retries:5 - Number of times to retry a request to a broker yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.retry_base_backoff_ms:100 - Delay (in milliseconds) for initial retry backoff yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.sasl_mechanism: - The SASL mechanism to use when connecting yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.scram_password: - Password to use for SCRAM authentication mechanisms yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:437 - schema_registry_client.scram_username: - Username to use for SCRAM authentication mechanisms yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] syschecks - Writing pid file "/var/lib/redpanda/data/pid.lock" yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] storage - directories.h:33 - Checking /var/lib/redpanda/data for supported filesystems yyyy-mm-dd hh:mi:ss ERROR yyyy-mm-dd hh:mi:ss,sss [shard 0] syschecks - Path: `/var/lib/redpanda/data' is not on XFS. This is a non-supported setup. Expect poor performance. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:793 - Partition manager started yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] rpc - server.cc:253 - protocol not set - Stopping 0 listeners yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] rpc - server.cc:262 - protocol not set - Shutting down 0 connections yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:239 - Shutdown complete. yyyy-mm-dd hh:mi:ss INFO yyyy-mm-dd hh:mi:ss,sss [shard 0] redpanda::main - application.cc:255 - Failure during startup: std::__1::system_error (error C-Ares:4, kafka: Not found)

Additional Information

No response

eddumelendez commented 1 week ago

Hi @YanivKunda, can you please let me know me where are you trying to connect from? or explain the topology for your test?

YanivKunda commented 1 week ago

We use a shared component that wraps a RedpandaContainer, and it is used by tests that access it from the test itself (to the mapped port), from another container (to a custom port), or from both. We need the listener to provide access from another container, but if we just need to access it from the test the listener gets configured anyway.

In 1.20.1, this would work (using the now-deprecated overload), but in 1.20.2 it fails (using the new overload) - unless I define a network for the RP container. So creating a network is a workaround, but seems unnecessary.

I think the Docker engine fails to bind a listener to an IP other than 0.0.0.0 if there's no network defined (the deprecated overload created the listener on 0.0.0.0, which is why it probably work).

I'm not sure if there other/special hostnames/IPs Docker can bind to in absence of a network - But the fix might be to set the listener address using some logic, i.e. if the hostnames/IP can be bound to use it, otherwise use 0.0.0.0. Advertised listener should probably remain as is. I'm not sure it would work on all Docker implementations though.