[
https://issues.apache.org/jira/browse/IMPALA-12875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gaurav singh closed IMPALA-12875.
---------------------------------
Resolution: Abandoned
> Identify Coordinator HA from the web debug endpoint
> ---------------------------------------------------
>
> Key: IMPALA-12875
> URL: https://issues.apache.org/jira/browse/IMPALA-12875
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: gaurav singh
> Assignee: gaurav singh
> Priority: Major
>
> Identify which Coordinator pod is active from the web debug endpoint.
> For the HA, we should improve the label on coordinator web response to
> indicate "Active" instance.
> On the main page we could indicate "Status: Active" or "Status: Stand-by". We
> could probably add the status at the top of the main page before *"Version"*
> . The current details as output of a curl request on port 25000:
> {code:java}
> <h2>Impala Server Mode: Coordinator
> (Local Catalog Mode)
> </h2>
> <h2>Vers<span id="v">i</span>on</h2>
> <pre id="version_pre">impalad version 4.0.0.2024.0.18.0-61 RELEASE (build
> 82901f3f83fa4c25b318ebf825a1505d89209356)
> Built on Fri Mar 1 20:13:09 UTC 2024
> Build Flags: is_ndebug=true cmake_build_type=RELEASE
> library_link_type=STATIC </pre>
> <!-- The space after is necessary to add a space between each flag when
> this page is rendered --> <h2>Process Start Time</h2>
> <pre>2024-03-05 17:09:09.007435000</pre> {code}
> Coordinator active detection is a bit tricky as that's handled on K8s side.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
