lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (SOLR-1273) rectify confusing "Replication" and "Distribution" links on solr admin screen
Date Sun, 12 Jul 2009 17:57:14 GMT


Hoss Man commented on SOLR-1273:

We should keep the logic and information displayed on distributiondump.jsp available for people
who already use script based replication and want to upgrade to 1.4 (without switching to
java based replication.

My suggestion would be to use a servlet mapping to map the "distributiondump.jsp" path to
"replication/index.jsp" and add logic that JSP so that if no replication handler is registered,
then it falls back to looking for the data files from script based replication and displays

This could also simplify the logic in the admin screen -- instead of displaying the replication
link only when a handler is registered, the link could always be displayed, and the replication
JSP could then have a basic control flow of...

if (replicationHandlersRegistered) {
} else if (scriptReplicationDataFilesExist) {
} else {

> rectify confusing "Replication" and "Distribution" links on solr admin screen
> -----------------------------------------------------------------------------
>                 Key: SOLR-1273
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 1.4
>            Reporter: Hoss Man
>            Priority: Minor
>             Fix For: 1.4
> Sine 1.0, the Solr Admin screen has had a "Distribution" link which points to "distributiondump.jsp"
and displays stats according to data files created by the snappuller/snapinstaller scripts
> With the new java based replication, when a ReplicationHandler is enabled, we now have
a "Replication" link on the admin page pointing to "replication/index.jsp" which displays
stats/status for java based replication.
> In at least one instance, these two different links confused a user...
> We need to rectify this confusion prior to releasing 1.4.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message