Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-1912

Replication handler should offer more useful status messages, especially during fsync/commit/etc.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Cannot Reproduce
    • 1.4
    • None
    • replication (java)
    • None

    Description

      If you go to the replication admin page (http://server:port/solr/core/admin/replication/index.jsp) while replication is in progress, then you'll see a "Current Replication Status" section, which indicates how far along the replication download is, both overall and for the current file. It's great to see this status info. However, the replication admin page becomes misleading once the last file has been downloaded. In particular, after all downloads are complete Solr 1.4 continues to display things like this:

      Downloading File: _wv_1.del, Downloaded: 44 bytes / 44 bytes [100.0%]

      until all the index copying, fsync-ing, committing, and so on are complete. It gives the disconcerting impression that data transfer between master and slaves has mysteriously stalled right at the end of a 44 byte download. In case this is weird, let me mention that after a full replication I did just now, Solr spent quite a while in SnapPuller.terminateAndWaitFsyncService(), somewhere between many seconds and maybe 5 minutes.

      I propose that the admin page should offer more useful status messages while fsync/etc. are going on. I offer an initial patch that does this. SnapPuller is modified to always offer a human readable indication of the "current operation", and this is displayed on the replication page. We also stop showing progress indication for the "current file", except when there actually is a file currently being downloaded.

      Attachments

        1. SOLR-1912.patch
          15 kB
          Chris Harris

        Activity

          People

            Unassigned Unassigned
            ryguasu Chris Harris
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: