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

Sometimes data is not replicated to replica slices which are added to a SolrCloud cluster which runs without replica

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Cannot Reproduce
    • 4.0-ALPHA
    • 4.9, 6.0
    • replication (java)
    • Linux 2.6.32-29-server #58-Ubuntu SMP Fri Feb 11 21:06:51 UTC 2011 x86_64 GNU/Linux, Solr snapshot from 29th of February 2012, 2 Solr machines with 1 slice each and 0 replica

    Description

      Scenario: ensure that replica slices specified in the configuration are added on sequential node restart without loosing data
      Given a SolrCloud cluster is running with
      number of servers (Solr nodes): 2
      number of slices per node: 1
      number of replica per slice: 0
      number of documents in leader slice on first Solr node: 4
      number of documents in leader slice on second Solr node: 1
      When I configure each node with 1 replica per slice
      And I restart the nodes one at a time
      Then I would expect that the SolrCloud cluster is running with
      number of servers (Solr nodes): 2
      number of slices per node: 1
      number of replica per slice: 1
      number of documents in leader slice on first Solr node: 4
      number of documents in replica slice on second Solr node: 4
      number of documents in leader slice on first Solr node: 1
      number of documents in replica slice on second Solr node: 1

      Testresult: the scenario has been performed several times with success however sometimes data is not replicated; it has been observed that sometimes no data is replicated at all and sometimes only data from one of the slices is replicated

      Attachments

        Activity

          People

            Unassigned Unassigned
            jensbor Jens Bo Rasmussen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 120h
                120h
                Remaining:
                Remaining Estimate - 120h
                120h
                Logged:
                Time Spent - Not Specified
                Not Specified