Hi, I have a feeling we're facing a similar issue (about which I posted separately). The behaviour is like the routing that applied before (in our case explicit on some indexes and just on _id for others) when the document was indexed, doesn't now resolve to the same shard following a cluster upgrade from 1.1.1 to 1.2. The data didn't change, only the ES version and the configuration is automatically deployed so I don't believe that can be the issue either.
I hope to be able to find time to reproduce the issue on a smaller scale but it's painful as it involves ES software upgrade. Neil On Monday, 26 May 2014 08:47:41 UTC+1, Pir Abdul Rasool Qureshi wrote: > > Hi > > We have a single machine elastic search server (8 shards but all hosted at > the same machine). Index contains 7 million documents. We do not specify > any custom routing when indexing the documents. We are using Elastic search > version 1.2. > > The problem is that we are unable to retrieve many of our documents using GET > <the id>, . However using search?_id:<the id> we are able to retrieve all > of those documents. > > We are also successful in retrieving a document by specifying routing > parameter (with different values (1,2,3,...) ) with GET. > > With previous version, i.e. Elastic Search 1.0.3, we did not have that > problem. > > Any suggestions for resolution? > > Thanks in advance > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/109aefe5-8074-499f-a7f3-88c6254b1b85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
