Skip to content

Conversation

@thinkharderdev
Copy link
Contributor

…v6 addresses

Which issue does this PR close?

Fixes #1020

Closes #.

Closes #1020

Rationale for this change

Currently when using Ballista standalone, the standalone executor does not send its local IP when registering metadata with the scheduler. The scheduler will default to the IPv4 caller address even though the executor is listening on the IPv6 loopback address (on some platforms). This will cause clients to fail to fetch partitions when they try and call the flight service on the IPv4 socket instead of the IPv6 socket.

What changes are included in this PR?

Standalone executor should explicitly return it's local IP address when registering metadata

Are there any user-facing changes?

I don't think so.

I don't think so.

@houqp houqp added the bug Something isn't working label Dec 19, 2021
@houqp houqp merged commit ecfc7d8 into apache:master Dec 22, 2021
@thinkharderdev thinkharderdev deleted the issue/1020 branch December 22, 2021 14:22
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

Successfully merging this pull request may close these issues.

Ballista context::tests::test_standalone_mode test fails

3 participants