[
https://issues.apache.org/jira/browse/SOLR-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 SimpleOrderedMap<Object>() );
}
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.
