[jira] [Commented] (SOLR-1364) Distributed search return Solr shard header information (like qtime)
[ https://issues.apache.org/jira/browse/SOLR-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068653#comment-16068653 ] Erick Erickson commented on SOLR-1364: -- Also isn't some of this info returned if you set shards.info=true? > Distributed search return Solr shard header information (like qtime) > > > Key: SOLR-1364 > URL: https://issues.apache.org/jira/browse/SOLR-1364 > Project: Solr > Issue Type: Improvement > Components: search >Affects Versions: 1.4 >Reporter: Jason Rutherglen >Priority: Minor > Fix For: 4.9, 6.0 > > Attachments: SOLR-1364.patch > > Original Estimate: 72h > Remaining Estimate: 72h > > Distributed queries can expose the Solr shard query information > such as qtime. The aggregate qtime can be broken up into the > time required for each stage. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-1364) Distributed search return Solr shard header information (like qtime)
[
https://issues.apache.org/jira/browse/SOLR-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068035#comment-16068035
]
Jan Høydahl commented on SOLR-1364:
---
Is this still needed in these days of SolrCloud, Metrics APIs and auto
rebalance rules?
I could see the use of a {{debugShards=true}} perhaps?
> Distributed search return Solr shard header information (like qtime)
>
>
> Key: SOLR-1364
> URL: https://issues.apache.org/jira/browse/SOLR-1364
> Project: Solr
> Issue Type: Improvement
> Components: search
>Affects Versions: 1.4
>Reporter: Jason Rutherglen
>Priority: Minor
> Fix For: 4.9, 6.0
>
> Attachments: SOLR-1364.patch
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Distributed queries can expose the Solr shard query information
> such as qtime. The aggregate qtime can be broken up into the
> time required for each stage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Commented: (SOLR-1364) Distributed search return Solr shard header information (like qtime)
[ https://issues.apache.org/jira/browse/SOLR-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12838473#action_12838473 ] ian connor commented on SOLR-1364: -- Hi Jason, this patch is not that good. It does expose where you can capture that information - but does not report it on each request. Instead, it adds it to the statistics page and calculates a running average, total and count per shard. It will at least help you see if you have a hot shard that is on average taking a long time. Distributed search return Solr shard header information (like qtime) Key: SOLR-1364 URL: https://issues.apache.org/jira/browse/SOLR-1364 Project: Solr Issue Type: Improvement Components: search Affects Versions: 1.4 Reporter: Jason Rutherglen Priority: Minor Fix For: 1.5 Attachments: SOLR-1364.patch Original Estimate: 72h Remaining Estimate: 72h Distributed queries can expose the Solr shard query information such as qtime. The aggregate qtime can be broken up into the time required for each stage. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1364) Distributed search return Solr shard header information (like qtime)
[ https://issues.apache.org/jira/browse/SOLR-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12838557#action_12838557 ] ian connor commented on SOLR-1364: -- Good idea. Here is some sample out put on a solr stats page. description: The standard Solr request handler stats: handlerStart : 1267037173182 requests : 3099817 errors : 2221 timeouts : 0 totalTime : 52082310 avgTimePerRequest : 16.801737 standardDeviation : 304.06168 avgRequestsPerSecond : 31.80935 10.0.16.181:8895/solr_numRequests : 12869 10.0.16.181:8884/solr_averageQTime : 9.651404 10.0.16.181:8896/solr_queryTime : 314763 10.0.16.181:8896/solr_elapsedTime : 681581 10.0.16.181:8885/solr_elapsedTime : 193555 10.0.16.181:8882/solr_elapsedTime : 329673 10.0.16.181:8898/solr_elapsedTime : 519454 10.0.16.181:8896/solr_queryQTime : 0 10.0.16.181:8897/solr_numRequests : 15344 10.0.16.181:8885/solr_queryTime : 62374 10.0.16.181:8891/solr_elapsedTime : 549124 10.0.16.181:8884/solr_elapsedTime : 367643 10.0.16.181:8898/solr_queryTime : 183239 10.0.16.181:8885/solr_averageQTime : 11.983478 10.0.16.181:/solr_averageQTime : 52.41645 10.0.16.181:8892/solr_averageQTime : 25.302937 10.0.16.181:8887/solr_queryQTime : 101 etc. From this sample, we can see 10.0.16.181:8892 average is only 25ms where 10.0.16.181: is at 52ms (twice as much) so we might consider rebalancing the shards to give 10.0.16.181: less work. Ideally, it would be good to get individual times to also go back on the request to the client so that these could be tracked and to see if any patterns emerge (certain queries hurt certain shards or the time might correspond to a replication event). If someone wants to take these times and put on them on the request - that would be brilliant (I did not figure that part out yet). Distributed search return Solr shard header information (like qtime) Key: SOLR-1364 URL: https://issues.apache.org/jira/browse/SOLR-1364 Project: Solr Issue Type: Improvement Components: search Affects Versions: 1.4 Reporter: Jason Rutherglen Priority: Minor Fix For: 1.5 Attachments: SOLR-1364.patch Original Estimate: 72h Remaining Estimate: 72h Distributed queries can expose the Solr shard query information such as qtime. The aggregate qtime can be broken up into the time required for each stage. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1364) Distributed search return Solr shard header information (like qtime)
[
https://issues.apache.org/jira/browse/SOLR-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12829803#action_12829803
]
ian connor commented on SOLR-1364:
--
I agree, to find hot shards and better debug a complex distributed system -
this is essential.
If the shard and elapsedTime were made public off the request, you could pull
them from the srsp in SearchHandler.java
long elapsedTime = srsp.getElapsedTime();
String shard = srsp.getShard();
some_hashmap_of_shard_times.set(shard, elapsedTime);
then you could report them back I think with code like:
// add the timing info
if( rb.getDebugInfo() == null ) {
rb.setDebugInfo( new SimpleOrderedMapObject() );
}
rb.getDebugInfo().add( shardtimes, some_hashmap_of_shard_times );
However, I am not sure if debugInfo takes a HashMap or if a different object
would be better suited.
Distributed search return Solr shard header information (like qtime)
Key: SOLR-1364
URL: https://issues.apache.org/jira/browse/SOLR-1364
Project: Solr
Issue Type: Improvement
Components: search
Affects Versions: 1.4
Reporter: Jason Rutherglen
Priority: Minor
Fix For: 1.5
Original Estimate: 72h
Remaining Estimate: 72h
Distributed queries can expose the Solr shard query information
such as qtime. The aggregate qtime can be broken up into the
time required for each stage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1364) Distributed search return Solr shard header information (like qtime)
[ https://issues.apache.org/jira/browse/SOLR-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755832#action_12755832 ] Jason Rutherglen commented on SOLR-1364: I'm adding debugging to this issue, where if debugQuery=true or debugShards=true then the results will basically list the returned response headers from each shard. Also needed, is which shard each debug entry is from. Otherwise distributed queries become rather difficult to regulate. Distributed search return Solr shard header information (like qtime) Key: SOLR-1364 URL: https://issues.apache.org/jira/browse/SOLR-1364 Project: Solr Issue Type: Improvement Components: search Affects Versions: 1.4 Reporter: Jason Rutherglen Priority: Minor Fix For: 1.5 Original Estimate: 72h Remaining Estimate: 72h Distributed queries can expose the Solr shard query information such as qtime. The aggregate qtime can be broken up into the time required for each stage. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
