Github user joshelser commented on the issue:
https://github.com/apache/accumulo/pull/242
> What has changed is that the standby serves the REST API and views
instead of displaying a message that it does not have the lock, while it is
waiting for the lock.
An old, standby monitor would return HTTP/503 (unavailable) to signify that
it isn't polling data from the master and (thus) is useless to observe. Does
the new REST API still do this?
I am thinking that the test could hit the REST API (instead of a view) to
get the same HTTP/503, and the view could display its message about "i am the
standby-monitor, blah blah" in response to the 503?
Aside: I'm finding the use of 503 to denote "expected unavailability" to be
odd (i'm used to 5xx series being unexpected server-side errors) despite using
that code when writing this :). I wonder if there is a 4xx response code which
would be more appropriate.
---
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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
