stribute the load or if a particular shard replica goes down then you
> want to add another Replica back for the shard in which case ADDREPLICA
> requires a shard name?
>
> Can you describe your scenario / provide more detail?
>
> Thanks,
> Susheel
>
>
>
> On
g/confluence/display/solr/CoreAdmin+API
>for SolrCloud.
>
>Hope that clarifies and you mentioned about ADDREPLICA which is the
>collections API, so you are on right track.
>
>Thanks,
>Susheel
>
>
>
>On Sun, Feb 14, 2016 at 10:51 AM, McCallick, Paul <
>paul.e.mcc
out on the user. This can be challenging in an autoscale scenario.
Thanks,
Paul
> On Feb 14, 2016, at 12:25 AM, Shawn Heisey wrote:
>
>> On 2/13/2016 6:01 PM, McCallick, Paul wrote:
>> - When creating a new collection, SOLRCloud will use all available nodes for
>> the
I’d like to verify the following:
- When creating a new collection, SOLRCloud will use all available nodes for
the collection, adding cores to each. This assumes that you do not specify a
replicationFactor.
- When adding new nodes to the cluster AFTER the collection is created, one
must use
eisey" wrote:
>On 2/10/2016 10:33 AM, McCallick, Paul wrote:
>> We’re trying to fine tune our query and ingestion performance and would like
>> to get more metrics out of SOLR around this. We are capturing the standard
>> logs as well as the jetty request logs. The standa
We’re trying to fine tune our query and ingestion performance and would like to
get more metrics out of SOLR around this. We are capturing the standard logs
as well as the jetty request logs. The standard logs get us QTime, which is
not a good indication of how long the actual request took to
