lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Au (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3986) index version and generation not changed in admin UI after delete by query on master
Date Wed, 24 Oct 2012 14:34:13 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483273#comment-13483273
] 

Bill Au commented on SOLR-3986:
-------------------------------

By the way, the request URL for the summary screen for core collection1:

localhost:8983/solr/#/collection1

the request URL for the replication screen:

localhost:8983/solr/#/collection1/replication
                
> index version and generation not changed in admin UI after delete by query on master
> ------------------------------------------------------------------------------------
>
>                 Key: SOLR-3986
>                 URL: https://issues.apache.org/jira/browse/SOLR-3986
>             Project: Solr
>          Issue Type: Bug
>          Components: web gui
>    Affects Versions: 4.0
>            Reporter: Bill Au
>            Priority: Minor
>
> Here are the steps to reproduce this:
> - follow steps in Solr 4.0 tutorial to set up a master and a slave to use Java/HTTP replication
> - index example documents on master:
> java -jar post.jar *.xml
> - make a note of the index version and generation the on both the replication section
of the summary screen of core collection1 and the replication screen on both the master and
slave
> - run a delete by query on the master
> java -Ddata=args -jar post.jar "<delete><query>name:DDR</query></delete>"
> - on master reload the summary screen for core collection1.  The Num Docs field decreased
but the index version and generation are unchanged in the replication section.  The index
version and generation are also unchanged in the replication screen.
> - on the slave, wait for replication to kick in or trigger it manually.  On the summary
screen for core collection1, the Num DOcs field decreased to match what's on the master. 
The index version and generation of the master remain unchanged but the index version and
generation of the slave both changed.  The same goes for the index version and generation
of the master and slave on the replication screen.
> The replication handler on the master does report changed index version and generation:
> localhost:8983/solr/collection1/replication?command=indexversion
> It is only the admin UI that reporting the older index version and generation on both
the core summary screen and replication screen.
> This only happens with delete by query.  There is no problem with delete with id or add.
> Both the index version and generation do get updated on subsequent delete by query but
both remain one cycle behind on the master.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message