Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Fixed #500: linking sample tasks to bootstrap host by default #785

Merged
merged 2 commits into from
Jun 13, 2017

Conversation

grtjn
Copy link
Contributor

@grtjn grtjn commented Jun 7, 2017

Fixes #500

@grtjn grtjn added this to the July 2017 milestone Jun 7, 2017
@@ -104,6 +104,9 @@ def initialize(options)
else
@qconsole_port = @bootstrap_port
end

r = execute_query %Q{xdmp:host-name()}
@properties["ml.server-name"] = parse_body(r.body)
Copy link
Contributor

Choose a reason for hiding this comment

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

Seems like this would also have the side effect of not allowing people to hit their load balancer? Couldn't that potentially be unwanted behavior for tools like MLCP?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Can you elaborate? Keep in mind server-name is only used within ml-config. We will remain using ml.server to make http/xcc calls..

Copy link
Contributor

Choose a reason for hiding this comment

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

You're correct, I confused the two properties

@grtjn
Copy link
Contributor Author

grtjn commented Jun 12, 2017

Yeah, the ml.server-name property is new, and not read from properties yet. I could add that though, as option. And I need to make the xqy call a bit more robust. (capture exceptions if ml cannot be reached or such..)

@RobertSzkutak
Copy link
Contributor

This is fine for me. Appeared to work correctly and didnt seem to break anything.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants