Thanks for contributing and I'm glad we got this fixed together :-) On Mon, Aug 3, 2026 at 3:01 AM Olivier Boudet <[email protected]> wrote:
> Hi Solr community, > > I encountered an issue during a SPLITSHARD operation on a collection > configured with custom routing via router.field. Existing documents are not > being migrated to the new sub-shards, leaving them empty. > Summary of the issue > > - > > *Collection setup:* router.name: compositeId with a custom field > router.field: > "company_id" (type plong ). > - > > *Operation:* Executing a SPLITSHARD command (tested with > numSubShards=4). > - > > *Observed Behavior:* > 1. > > The API returns status: 0 (Success) almost instantly. > 2. > > New sub-shards are created and set to active, while parent shards > become inactive. > 3. > > However, *existing documents are not copied over* to the new > sub-shards. They remain stuck in the inactive parent shards and > become > unsearchable. Sub-shards only receive newly indexed documents > post-split. > > Minimal Reproducer > > I have created a minimal reproducer repository with a basic schema and the > exact steps to reproduce the issue: > https://github.com/olivierboudet/solr-splitshard-test/tree/main > > All execution steps and commands are detailed in the README.md. > > This behavior seems to be consistently reproducible (at least when > using router.field > of type plong with compositeId). Could this be a bug or I > misconfigured something ? > > Has anyone experienced this before, do you think it worth opening a JIRA > issue ? > > Thanks for your help! > > Best regards, > > Olivier >
