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

MINOR: Trogdor should not assume an agent co-located with the controller #4712

Merged
merged 2 commits into from
Mar 16, 2018

Conversation

cmccabe
Copy link
Contributor

@cmccabe cmccabe commented Mar 14, 2018

No description provided.

@@ -33,7 +33,7 @@
public static Set<String> agentNodeNames(Topology topology) {
Set<String> set = new HashSet<>();
for (Map.Entry<String, Node> entry : topology.nodes().entrySet()) {
if (Node.Util.getTrogdorAgentPort(entry.getValue()) > 0) {
if (entry.getValue().getConfig(Platform.Config.TROGDOR_AGENT_PORT) != null) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the test failure in the PR builds are related to this change. MiniTrogdorCluster used in the tests sets agent port to zero on the coordinator, so this check doesn't work?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Fixed

Copy link
Contributor

@rajinisivaram rajinisivaram left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cmccabe Thanks for the update, LGTM. Merging to trunk.

@rajinisivaram rajinisivaram merged commit 9e0e6e4 into apache:trunk Mar 16, 2018
@cmccabe cmccabe deleted the do_not_assume_colocation branch May 20, 2019 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants