Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/680
+1 (non-binding).
Validated the latest fix to be working great. Thank you, @dlyle65535 .
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/680
Sounds great, @dlyle65535 !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
Oh yeah, thanks for clarifying, @anandsubbu - I'm not going to change the
'happy path' logic, so when the UI is up, it will work the way it did prior.
---
If your project is set up for it, you
Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/680
Hi @dlyle65535 can it be a two step validation as follows:
a) We first verify if we are able to hit the storm URL, if that fails ->
then we mark the service as stopped.
b) If the storm
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
I'm starting to think the best approach would to assume the service is
stopped if we can't get to the ui (which we kind of do anyway because of how
status works).
Anybody absolutely hate
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/680
@dlyle65535 Thanks for the update. That's pretty surprising, it seems like
this should take care of it. Ping me when there's some new info, and I'll hop
back on this review.
---
If your
