Solr
  1. Solr
  2. SOLR-3527

SolrCmdDistributor drops some of the important commit attributes (maxOptimizeSegments, softCommit, expungeDeletes) when sending a commit to replicas.

    Details

      Description

      Send the following command to a Solr server with many segments in a multi-shard, multi-server environment:

      curl "http://localhost:8080/solr/update?optimize=true&waitFlush=true&maxSegments=6&distrib=false"

      The local server will end up with the number of segments at 6, as requested, but all other shards in the index will be optimized with maxSegments=1, which takes far longer to complete. All shards should be optimized to the requested value of 6.

        Activity

        Andy Laird created issue -
        Mark Miller made changes -
        Field Original Value New Value
        Assignee Mark Miller [ markrmiller@gmail.com ]
        Mark Miller made changes -
        Fix Version/s 4.0 [ 12322551 ]
        Fix Version/s 5.0 [ 12321664 ]
        Priority Major [ 3 ] Critical [ 2 ]
        Component/s SolrCloud [ 12313841 ]
        Mark Miller made changes -
        Summary Optimize ignores maxSegments in distributed environment SolrCmdDistributor drops some of the important commit attributes (maxOptimizeSegments, softCommit, expungeDeletes) when sending a commit to replicas.
        Mark Miller made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Uwe Schindler made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Mark Miller
            Reporter:
            Andy Laird
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development