Hi,
the only way that i find to solve my problem is to do the split using a
solr instance configured in standalone mode.
curl
http://localhost:8983/solr/admin/cores?action=SPLIT=sepa=/nas_perf_2/FRAGMENTS/17MINDEXES/1/index=/nas_perf/FRAGMENTS/17MINDEXES/2/index
In solr_cloud mode does the
Hi,
the only way that i find to solve my problem is to do the split using a
solr instance configured in standalone mode.
curl
http://localhost:8983/solr/admin/cores?action=SPLIT=sepa=/nas_perf_2/FRAGMENTS/17MINDEXES/1/index=/nas_perf/FRAGMENTS/17MINDEXES/2/index
In solr_cloud mode does the
Hi Shawn,
I'm looking for the docs num from the core overview page and the situation
is:
Num Docs: 35031923Max Doc: 35156879
The difference doesn't explain the strange behavior.
On Mon, Dec 28, 2015 at 1:35 AM, Shawn Heisey wrote:
> On 12/26/2015 11:21 AM, Luca
I don't use Curl but there are a couple of things that come to mind
1: Maybe use document routing with the shards. Use an "!" in your unique
ID. I'm using gmail to read this and it sucks for searching content so if
you have done this please ignore this point. Example: If you were storing
On 12/26/2015 11:21 AM, Luca Quarello wrote:
> I have a SOLR 5.3.1 CLOUD with two nodes and 8 shards per node.
>
> Each shard is about* 35 million documents (**35025882**) and 16GB sized.*
>
>
>- I launch the SPLIT command on a shard (shard 13) in the ASYNC way:
> The new created shards
Hi,
I have a SOLR 5.3.1 CLOUD with two nodes and 8 shards per node.
Each shard is about* 35 million documents (**35025882**) and 16GB sized.*
- I launch the SPLIT command on a shard (shard 13) in the ASYNC way:
curl "