Mapping routing keys to shards

Is there an easy way to tell which routing keys map to which shards?
I understand the algorithm is something like hash(routing_key) %
shard_count but I was hoping for a "trace" API of sorts to figure out
where my requests are actually ending up. Trying to nail down some
performance issues.

Thanks,
-Tim

First, the stats APIs (node and index level) can give you doc counts and
sizes per shard, this might help. You could turn index.engine debug level
to TRACE and see actual index operations (though its not recommended to
keep it on).

On Thu, May 24, 2012 at 5:02 PM, Tim J jones.timothy.r@gmail.com wrote:

Is there an easy way to tell which routing keys map to which shards?
I understand the algorithm is something like hash(routing_key) %
shard_count but I was hoping for a "trace" API of sorts to figure out
where my requests are actually ending up. Trying to nail down some
performance issues.

Thanks,
-Tim