Healthcheck on different port? about bamboo HOT 12 CLOSED

Does Marathon allow you to specify health checks on multiple ports?

from bamboo.

Yep: you can define multiple health checks, each with its own portIndex:
https://mesosphere.github.io/marathon/docs/health-checks.html

from bamboo.

This might also related to running multiple port apps in single Marathon task (e.g. via docker)
Ideally each healthcheck and each app port will be generated in the template.

I can confirm your request is in the roadmap - it's slightly tricky to implement it in the correct way. I will start writing some basic requirements related to this feature and implementation plan somewhere.

from bamboo.

Thanks, let me know if I can provide any more info!

from bamboo.

@activars: I see you added the waiting for response label. Is there anything we can provide to help move forward with this issue?

We are also interested in Bamboo support for health-checking a different port. Let us know if there's anything we can do to assist you folks.

Thanks!

from bamboo.

To support this, I would like to support multiple healthchecks per backend server. For example, a Marathon app may have checks for TCP port 3000 and HTTP port 4000. Both check should be reflected to HAproxy routing logic.

This means, Bamboo needs to be refactored to support array of healthchecks:

• support HTTP
• support TCP
• possible command check (as Marathon support this)

I wonder if there is an workaround. So, instead of actually checking them (reinvent the wheel), it would be great just let HAProxy validate the application status from Marathons API, thus a single check will reflect the status of the service.

from bamboo.

@activars Sounds promising. Marathon does publish health check changes through its event bus, so Bamboo could tap into that. I agree that doubling the check seems unnecessary for backends that already take care of service healthiness.

Need help implementing? I could take a stab.

from bamboo.

Hi, I'm open to PRs and any contributions.

On 13 Mar 2015, at 19:20, Timo Reimann [email protected] wrote:

@activars https://github.com/activars Sounds promising. Marathon does publish
health check changes through its event bus
https://mesosphere.github.io/marathon/docs/event-bus.html, so Bamboo
could tap into that. I agree that doubling the check seems unnecessary for
backends that already take care of service healthiness.

Need help implementing? I could take a stab.

—
Reply to this email directly or view it on GitHub
#62 (comment).

from bamboo.

Did you implement this?

from bamboo.

No, I'm merging this issue with the healthcheck improvements. Duplicate #57
I think this also relates to multiple service ports, api and ui improvements. I need to think about refactoring and not breaking existing APIs.

from bamboo.

Okay, makes sense. It's just that #57 does not explicitly mention the idea of supporting multiple ports, which I think was the original intention for this issue.

(Although I'm more interested in the "just reuse health checks from Marathon" idea by know because that seems to be the right approach.)

from bamboo.

I agree with your suggestion. I don't want to reimplement the robust featured healthcheck that marathon provides.

from bamboo.