[
https://issues.apache.org/jira/browse/IGNITE-20150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750999#comment-17750999
]
Ivan Zlenko commented on IGNITE-20150:
--------------------------------------
[~aleksandr.pakhomov] IGNITE-20156 created
> JDBC port not exposed in docker-compose.yml in Ignite 3
> -------------------------------------------------------
>
> Key: IGNITE-20150
> URL: https://issues.apache.org/jira/browse/IGNITE-20150
> Project: Ignite
> Issue Type: Bug
> Components: build
> Affects Versions: 3.0.0-beta2
> Reporter: Ivan Zlenko
> Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ignite has an option to run cluster inside Docker container. To run several
> nodes we can use docker compose file. In repo exists pre-defined
> docker-compose.yml and example could be found in documentation. However both
> file from repo and docs contains one simple error: JDBC port is not exposed.
> So as soon as someone will try to enter SQL mode inside CLI following error
> will be received:
> {code}
> [node1]> sql
> 196609 Trace ID: 2c6f842d-2d08-4b51-b1cf-307e664dc9ff
> Connection failed
> Client failed to connect: Connection refused: localhost/127.0.0.1:10800
> {code}
> Adding 10800 into docker-compose file fixes that problem.
> On the side note: I'm not sure if it is necessary to expose ScaleCube ports
> externally. As far as I understand they exists only for internal
> communication between nodes and no one should connect to those ports
> externally.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
