Hi all,
I'm trying to figure out how to shard our index as it is growing rapidly
and we want to make our solution scalable.
So, we have documents that are most commonly sorted by their date. My
initial thought is to shard the index by date, but I wonder if you have
any input on this and how to best solve this...
I know that the most frequent queries will be executed against the
"latest" shard, but then let's say we shard by year, how do we best solve
the situation that will occur in the beginning of a new year? (Some of the
data will be in the last shard, but most of it will be on the second last
shard.)
Would it be stupid to have a "latest" shard with duplicate data (always
consisting of the last 6 months or something like that) and maintain that
index in addition to the regular yearly shards? Any one else facing a
similar situation with a good solution?
Any input would be greatly appreciated :)
Cheers,
Aleksander
--
Aleksander M. Stensby
Lead software developer and system architect
Integrasco A/S
www.integrasco.no
http://twitter.com/Integrasco
Please consider the environment before printing all or any of this e-mail
