You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Webster Homer <we...@sial.com> on 2017/05/10 14:34:39 UTC
Solrcloud collection restore puts 2 replicas on the same node
I am running Solr 6.2 on a 4 node cluster
Each collection has 2 shards and a replication factor of 2
Normally when I create a collection I see a replica on each node, which is
what I would expect.
However when I restore a backup to a new collection I see that one node has
two replicas on it. They are from different shards, but one of my nodes
doesn't get a replica. Is there a way to force the restore to use different
nodes if it can?
I saw a similar issue on a two node test cloud where the restore created
the two replicas on the same node.
--
This message and any attachment are confidential and may be privileged or
otherwise protected from disclosure. If you are not the intended recipient,
you must not copy this message or attachment or disclose the contents to
any other person. If you have received this transmission in error, please
notify the sender immediately and delete the message and any attachment
from your system. Merck KGaA, Darmstadt, Germany and any of its
subsidiaries do not accept liability for any omissions or errors in this
message which may arise as a result of E-Mail-transmission or for damages
resulting from any unauthorized changes of the content of this message and
any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its
subsidiaries do not guarantee that this message is free of viruses and does
not accept liability for any damages caused by any virus transmitted
therewith.
Click http://www.emdgroup.com/disclaimer to access the German, French,
Spanish and Portuguese versions of this disclaimer.
Re: Solrcloud collection restore puts 2 replicas on the same node
Posted by Erick Erickson <er...@gmail.com>.
bq; When will 6.6 be released
Real Soon Now. The release process has started, the first RC will
probably be cut sometime next week. After that, the process will take
3-4 days. Any issues found will reset that "3-4 days" as another RC is
spun.
Best,
Erick
On Wed, May 10, 2017 at 8:04 AM, Webster Homer <we...@sial.com> wrote:
> Yes that looks like the issue I'm seeing. When will 6.6 be released?
>
> On Wed, May 10, 2017 at 9:42 AM, Erick Erickson <er...@gmail.com>
> wrote:
>
>> Possibly https://issues.apache.org/jira/browse/SOLR-9527?
>>
>> On Wed, May 10, 2017 at 7:34 AM, Webster Homer <we...@sial.com>
>> wrote:
>> > I am running Solr 6.2 on a 4 node cluster
>> >
>> > Each collection has 2 shards and a replication factor of 2
>> >
>> > Normally when I create a collection I see a replica on each node, which
>> is
>> > what I would expect.
>> >
>> > However when I restore a backup to a new collection I see that one node
>> has
>> > two replicas on it. They are from different shards, but one of my nodes
>> > doesn't get a replica. Is there a way to force the restore to use
>> different
>> > nodes if it can?
>> >
>> > I saw a similar issue on a two node test cloud where the restore created
>> > the two replicas on the same node.
>> >
>> > --
>> >
>> >
>> > This message and any attachment are confidential and may be privileged or
>> > otherwise protected from disclosure. If you are not the intended
>> recipient,
>> > you must not copy this message or attachment or disclose the contents to
>> > any other person. If you have received this transmission in error, please
>> > notify the sender immediately and delete the message and any attachment
>> > from your system. Merck KGaA, Darmstadt, Germany and any of its
>> > subsidiaries do not accept liability for any omissions or errors in this
>> > message which may arise as a result of E-Mail-transmission or for damages
>> > resulting from any unauthorized changes of the content of this message
>> and
>> > any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its
>> > subsidiaries do not guarantee that this message is free of viruses and
>> does
>> > not accept liability for any damages caused by any virus transmitted
>> > therewith.
>> >
>> > Click http://www.emdgroup.com/disclaimer to access the German, French,
>> > Spanish and Portuguese versions of this disclaimer.
>>
>
> --
>
>
> This message and any attachment are confidential and may be privileged or
> otherwise protected from disclosure. If you are not the intended recipient,
> you must not copy this message or attachment or disclose the contents to
> any other person. If you have received this transmission in error, please
> notify the sender immediately and delete the message and any attachment
> from your system. Merck KGaA, Darmstadt, Germany and any of its
> subsidiaries do not accept liability for any omissions or errors in this
> message which may arise as a result of E-Mail-transmission or for damages
> resulting from any unauthorized changes of the content of this message and
> any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its
> subsidiaries do not guarantee that this message is free of viruses and does
> not accept liability for any damages caused by any virus transmitted
> therewith.
>
> Click http://www.emdgroup.com/disclaimer to access the German, French,
> Spanish and Portuguese versions of this disclaimer.
Re: Solrcloud collection restore puts 2 replicas on the same node
Posted by Webster Homer <we...@sial.com>.
Yes that looks like the issue I'm seeing. When will 6.6 be released?
On Wed, May 10, 2017 at 9:42 AM, Erick Erickson <er...@gmail.com>
wrote:
> Possibly https://issues.apache.org/jira/browse/SOLR-9527?
>
> On Wed, May 10, 2017 at 7:34 AM, Webster Homer <we...@sial.com>
> wrote:
> > I am running Solr 6.2 on a 4 node cluster
> >
> > Each collection has 2 shards and a replication factor of 2
> >
> > Normally when I create a collection I see a replica on each node, which
> is
> > what I would expect.
> >
> > However when I restore a backup to a new collection I see that one node
> has
> > two replicas on it. They are from different shards, but one of my nodes
> > doesn't get a replica. Is there a way to force the restore to use
> different
> > nodes if it can?
> >
> > I saw a similar issue on a two node test cloud where the restore created
> > the two replicas on the same node.
> >
> > --
> >
> >
> > This message and any attachment are confidential and may be privileged or
> > otherwise protected from disclosure. If you are not the intended
> recipient,
> > you must not copy this message or attachment or disclose the contents to
> > any other person. If you have received this transmission in error, please
> > notify the sender immediately and delete the message and any attachment
> > from your system. Merck KGaA, Darmstadt, Germany and any of its
> > subsidiaries do not accept liability for any omissions or errors in this
> > message which may arise as a result of E-Mail-transmission or for damages
> > resulting from any unauthorized changes of the content of this message
> and
> > any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its
> > subsidiaries do not guarantee that this message is free of viruses and
> does
> > not accept liability for any damages caused by any virus transmitted
> > therewith.
> >
> > Click http://www.emdgroup.com/disclaimer to access the German, French,
> > Spanish and Portuguese versions of this disclaimer.
>
--
This message and any attachment are confidential and may be privileged or
otherwise protected from disclosure. If you are not the intended recipient,
you must not copy this message or attachment or disclose the contents to
any other person. If you have received this transmission in error, please
notify the sender immediately and delete the message and any attachment
from your system. Merck KGaA, Darmstadt, Germany and any of its
subsidiaries do not accept liability for any omissions or errors in this
message which may arise as a result of E-Mail-transmission or for damages
resulting from any unauthorized changes of the content of this message and
any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its
subsidiaries do not guarantee that this message is free of viruses and does
not accept liability for any damages caused by any virus transmitted
therewith.
Click http://www.emdgroup.com/disclaimer to access the German, French,
Spanish and Portuguese versions of this disclaimer.
Re: Solrcloud collection restore puts 2 replicas on the same node
Posted by Erick Erickson <er...@gmail.com>.
Possibly https://issues.apache.org/jira/browse/SOLR-9527?
On Wed, May 10, 2017 at 7:34 AM, Webster Homer <we...@sial.com> wrote:
> I am running Solr 6.2 on a 4 node cluster
>
> Each collection has 2 shards and a replication factor of 2
>
> Normally when I create a collection I see a replica on each node, which is
> what I would expect.
>
> However when I restore a backup to a new collection I see that one node has
> two replicas on it. They are from different shards, but one of my nodes
> doesn't get a replica. Is there a way to force the restore to use different
> nodes if it can?
>
> I saw a similar issue on a two node test cloud where the restore created
> the two replicas on the same node.
>
> --
>
>
> This message and any attachment are confidential and may be privileged or
> otherwise protected from disclosure. If you are not the intended recipient,
> you must not copy this message or attachment or disclose the contents to
> any other person. If you have received this transmission in error, please
> notify the sender immediately and delete the message and any attachment
> from your system. Merck KGaA, Darmstadt, Germany and any of its
> subsidiaries do not accept liability for any omissions or errors in this
> message which may arise as a result of E-Mail-transmission or for damages
> resulting from any unauthorized changes of the content of this message and
> any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its
> subsidiaries do not guarantee that this message is free of viruses and does
> not accept liability for any damages caused by any virus transmitted
> therewith.
>
> Click http://www.emdgroup.com/disclaimer to access the German, French,
> Spanish and Portuguese versions of this disclaimer.