[
https://issues.apache.org/jira/browse/SOLR-18417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18120932#comment-18120932
]
Jason Gerlowski commented on SOLR-18417:
----------------------------------------
bq. it's not obvious when it's truly done
My aim was to create a deprecation PR that'd land on both 'main' and
'branch_10x' (now completed), and then do a removal PR that targets main only.
When both those are completed, I'd close this out as "done".
Let me know if that plan sounds "off" to anyone.
If there's some element of this that's non-obvious or could be clarified, let
me know!
> Deprecate and Remove PingRequestHandler
> ---------------------------------------
>
> Key: SOLR-18417
> URL: https://issues.apache.org/jira/browse/SOLR-18417
> Project: Solr
> Issue Type: Task
> Reporter: Jason Gerlowski
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 5h 40m
> Remaining Estimate: 0h
>
> Solr has a core-level API called the "PingRequestHandler". This API is meant
> to serve as a load-balancer healthcheck, but it has a few surprising quirks.
> Most significantly it operates at the core level rather than the node-level,
> so it requires load-balancers be aware of Solr's topology to some extent
> (which of course, very few off-the-shelf load balancers
> are.)
> For healthcheck purposes, PingRequestHandler has largely been superseded by
> the "System Info Handler" and the aptly named "Healthcheck Handler", which do
> some amount of health checking at the node-level.
> With PingRequestHandler largely vestigial, it's time to consider its removal.
> We should deprecate it in the current major version line (currently 10.x)
> and remove it entirely for the next one (currently 11.0).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
