: And with replication?command=details I also see the correct commit part as
: above, BUT where the hell are the wrong info below the commit array are
: coming from?
Please read the details in the previously mentioned Jira issue...
https://issues.apache.org/jira/browse/SOLR-4661
The indexVersio
Looking a bit deeper showed that replication?command=commit reports the
right indexversion, generation and filelist.
1365357951589
198
...
And with replication?command=details I also see the correct commit part as
above, BUT where the hell are the wrong info below the commit array are
c
Hi Hoss,
we don't use autoCommit and autoSoftCommit.
We don't use openSearcher.
We don't use transaction log.
I can see it in the AdminGUI and with
http://master_host:port/solr/replication?command=indexversion
All files are replicated from master to slave, nothing lost.
It is just that the gen/v
: I know there was some effort to fix this but I must report
: that solr 4.2.1 has still problems with index version and
: index generation numbering in master/slave mode with replication.
...
: RESULT: slave has different (higher) version number and is with generation 1
ahead :-(
Can you
This is the jira issue that addresses this:
https://issues.apache.org/jira/browse/SOLR-4661
I'll try to find some time today and test out the patch and see how things
look.
On Mon, Apr 8, 2013 at 7:18 AM, Tom Gullo wrote:
> I'm on 4.1 and I have a similar problem. Except for the version numb
I'm on 4.1 and I have a similar problem. Except for the version number
everything else seems to be fine. Is that what other people are seeing?
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-4-2-1-still-has-problems-with-index-version-and-index-generation-tp405p40
