Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hazelcast pings fail #2421

Open
eyalb181 opened this issue May 3, 2024 · 2 comments
Open

Hazelcast pings fail #2421

eyalb181 opened this issue May 3, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@eyalb181
Copy link
Member

eyalb181 commented May 3, 2024

Bug Description

When starting up, an app using Hazelcast tries to send ICMP pings and fails.

Steps to Reproduce

Run an app that uses Hazelcast. Initial pings will fail (you won't see them in the logs), and then it'll fallback to pinging over port 7.

Backtrace

No response

Relevant Logs

No response

Your operating system and version

N/A

Local process

N/A

Local process version

No response

Additional Info

No response

@eyalb181 eyalb181 added the bug Something isn't working label May 3, 2024
@aviramha
Copy link
Member

aviramha commented May 3, 2024

@aviramha
Copy link
Member

aviramha commented May 3, 2024

I think a temporary, patchy solution would be to emulate that connection to port 7 is always successful. If you look at the above example, tcp_ping4 just calls connect((host, 7)) and if it succeeds it closes and it is reachable from it's perspective.
We should add

{
"feature": {"experimental": {"tcp_ping4_mock": true}}
}

that will trigger that magic behavior for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants