[SOLR-4194] PingRequestHandler - shards parameter inherited from search handler definition

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 4.1

Environment

solr-impl 4.1-SNAPSHOT 1421496 - ncindex - 2012-12-13 14:56:25

• Assignee: Unassigned
• Reporter: Shawn Heisey
• Created: 14/Dec/12 22:35
• Updated: 19/Apr/13 19:38
• Resolved: 19/Apr/13 19:38

Description

Included in all my cores is a PingRequestHandler named /admin/ping, which I use to enable/disable the server from the perspective of a load balancer running haproxy. The handler includes a qt parameter set to /lbcheck.

I have a special core defined (I call it a broker) that includes the shards parameter in most of its search handler definitions. This includes /select, /lbcheck, and others.

When the /admin/ping handler is called, the query is sent to the /lbcheck parameter as expected, which gets distributed because it includes shards. If one of those shards happens to be down, the handler will give an error response to the load balancer.

The problem is that the PingRequestHandler seems to inherit the shards parameter from the search handler it is using, which causes the /admin/ping request itself to be distributed, which is not what I want. The individual shards are not used by the load balancer, so they always remain disabled.

This works perfectly in 3.5.0. The official 4.0.0 release has not been tested.

Config and log data will follow in the comments.

Issue Links

• is related to: SOLR-4143 setRequestHandler - option to not set qt parameter