apache / apache/ignite

2.14.0-arm64 does not work with custom host port

Open
#11,532 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
5.1k
Forks
1.9k
Avg merge
3d 2h
Merged PRs (30d)
46

Description

2.14.0-arm64 does not work with custom host port. Ignite client is able to discover the node but when simple "hello word" compute is done, it throws "message failed for node id", whereas simply changing the host port mapping from 47502:47500 to 47500:47500. On the emded client side I tried using both MultiCast IP finder and VImipfinder with the right ports, but it just don't work. Suspecting it is image issue. The same setup works outside of docker container, even with docker default ports mapping works just fine.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the 2.14.0-arm64 Docker setup with the 47502:47500 host-port mapping, using the Ignite client and the mentioned multicast or VM IP finder settings. Compare it with the working 47500:47500 mapping and the non-container setup; done means the client can complete the simple "hello word" compute without a "message failed for node id" error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java
Domain
distributed-systems, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.