Hmmm....Ok, I don't see how it's possible for me to ensure that there are no ties. If a query were for *:* everything has a constant score, if the user requested 1 page then requested the next the results on the second page could be duplicates from what was on the first page. I don't remember ever seeing this issue on older versions of SolrCloud, although from what you're saying I should have. What could explain why I never saw this before?
Another possible fix to ensure proper ordering couldn't we always specify a sort order which contained the key? So for instance the user asks for score asc, we'd make this score asc,key asc so that results would be order by score and then by key so the results across pages would be consistent? On Tue, Mar 20, 2012 at 11:30 AM, Yonik Seeley <yo...@lucidimagination.com> wrote: > On Tue, Mar 20, 2012 at 11:17 AM, Jamie Johnson <jej2...@gmail.com> wrote: >> ok, with my custom component out of the picture I still have the same >> issue. Specifically, when sorting by score on a leader and replica I >> am getting different doc orderings. Is this something anyone has >> seen? > > This is certainly possible and expected - sorting tiebreakers is by > internal lucene docid, which can change (even on a single node!) > If you need lists that don't shift around due to unrelated changes, > make sure you don't have any ties! > > -Yonik > lucenerevolution.com - Lucene/Solr Open Source Search Conference. > Boston May 7-10
