[
https://issues.apache.org/jira/browse/IGNITE-28811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Chesnokov updated IGNITE-28811:
-----------------------------------------
Description:
For now, it is unclear whether it is possible to connect a thick client or a
server node running outside Docker to a cluster running inside a Docker network.
For example, in one of the Medium articles, the author was also unable to
connect an external node to the cluster:
[https://medium.com/%40shamim_ru/apache-ignite-pitfalls-part-1-dockers-aed69e641c96]
and writes: {{First, a new Ignite client instance will be created, and it will
try to connect to the cluster but fail with errors}}
"Here we are stuck with the Ignite limitation: the thick client is not
compatible with this scenario. The reason is that the thick client is trying to
join the Ignite cluster but failed due to port forwarding."
>From my analysis, it also looks like there may be issues when connecting
>external nodes:
[https://github.com/apache/ignite/pull/13184/changes#r3450722241]
Let's improve the documentation:
[https://ignite.apache.org/docs/ignite2/latest/installation/installing-using-docker.html#running-in-memory-cluster]
and explicitly describe the limitations, supported scenarios, and possible
workarounds
was:
Code snippet for session context is invalid
{noformat}
try (Ignite ign = Ignition.start(ignCfg)) {
Map<String, String> appAttrs = F.asMap("SESSION_ID", "1234");
Ignite app = Ignite.withApplicationAttributes(appAttrs);
//Your code here...
}{noformat}
# F class is for private usage and is not part of public api
# We do not have static method Ignite to create node with attributes
> [doc] Add details about connection of external node to docker cluster
> ---------------------------------------------------------------------
>
> Key: IGNITE-28811
> URL: https://issues.apache.org/jira/browse/IGNITE-28811
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Aleksandr Chesnokov
> Assignee: Aleksandr Chesnokov
> Priority: Major
> Labels: IEP-129, doc, ise
> Fix For: 2.19
>
>
> For now, it is unclear whether it is possible to connect a thick client or a
> server node running outside Docker to a cluster running inside a Docker
> network.
> For example, in one of the Medium articles, the author was also unable to
> connect an external node to the cluster:
> [https://medium.com/%40shamim_ru/apache-ignite-pitfalls-part-1-dockers-aed69e641c96]
> and writes: {{First, a new Ignite client instance will be created, and it
> will try to connect to the cluster but fail with errors}}
> "Here we are stuck with the Ignite limitation: the thick client is not
> compatible with this scenario. The reason is that the thick client is trying
> to join the Ignite cluster but failed due to port forwarding."
> From my analysis, it also looks like there may be issues when connecting
> external nodes:
> [https://github.com/apache/ignite/pull/13184/changes#r3450722241]
> Let's improve the documentation:
> [https://ignite.apache.org/docs/ignite2/latest/installation/installing-using-docker.html#running-in-memory-cluster]
> and explicitly describe the limitations, supported scenarios, and possible
> workarounds
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
