You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "changxue (Jira)" <ji...@apache.org> on 2022/12/08 07:48:00 UTC
[jira] [Reopened] (IOTDB-5107) [confignode] cn_internal_address should not bind IP address
[ https://issues.apache.org/jira/browse/IOTDB-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
changxue reopened IOTDB-5107:
-----------------------------
Dec.8 master source codes, this issue still exists.
> [confignode] cn_internal_address should not bind IP address
> -----------------------------------------------------------
>
> Key: IOTDB-5107
> URL: https://issues.apache.org/jira/browse/IOTDB-5107
> Project: Apache IoTDB
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: changxue
> Assignee: 伊丹翔
> Priority: Major
> Attachments: image-2022-12-01-22-10-49-805.png
>
>
> [confignode] cn_internal_address should not bind IP address
> description:
> The docker container of config node start failed, because it do socket connection to itself – a16/172.20.31.16:22277
> a16 is the hostname of computer and the IP address upstairs is the real IP of computer.
> 我希望confignode只是使用我指定的域名进行绑定,而不是IP地址。因为IP地址有可能是container 的IP,也有可能是物理机的IP,如果只绑定一个,我将不能使用另一个。这样就不能使用bridge网络。只能使用host或者overlay网络。
> 与22278端口一样处理就很好。
> 启动confignode时日志:
> !image-2022-12-01-22-10-49-805.png|width=762,height=367!
> docker-compose.yml:
> {code:java}
> version: "3"
> services:
> iotdb-confignode:
> image: apache/iotdb:1.0.1-SNAPSHOT-confignode
> container_name: iotdb-confignode
> hostname: a16
> ports:
> - "22277:22277"
> - "22278:22278"
> environment:
> - cn_internal_address=a16
> - cn_target_config_node_list=a16:22277
> - schema_replication_factor=3
> - schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensu
> - config_node_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> volumes:
> - /etc/hosts:/etc/hosts:ro
> - ./data/confignode:/iotdb/data
> - ./logs/confignode:/iotdb/logs
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)