If your cluster is setup correctly (with proper value set 
for discovery.zen.minimum_master_nodes) they shouldn't. But if you are 
running without discovery.zen.minimum_master_nodes set, they might indeed 
form a new cluster. Obviously some shards might end up in one cluster and 
not in the other and if you are indexing while this is happening you will 
lose some data. I would say it's pretty..... extreme way to test full 
cluster restart. 

On Saturday, May 24, 2014 2:38:44 PM UTC-4, Andrew Vos wrote:
>
> Ok. While you're here, one other question I would like answered:
>
> I have 10 nodes in a cluster. I want to break out three nodes into a 
> different cluster as a kind of backup to test out this full cluster 
> restart. Would it be safe to just block the other three nodes from 
> connecting to the main cluster? Would they form their own?
>
>
> On Sat, May 24, 2014 at 7:35 PM, Igor Motov <[email protected]> wrote:
>
>> It was caused by this bug - 
>> https://github.com/elasticsearch/elasticsearch/issues/5958 The only 
>> recovery option right now is full cluster restart. 
>>
>> On Saturday, May 24, 2014 2:30:06 PM UTC-4, Andrew Vos wrote:
>>>
>>> Right ok here's the cluster state https://gist.github.com/
>>> AndrewVos/29de3c6735bbd7808a81
>>>
>>>
>>> On Sat, May 24, 2014 at 7:18 PM, Andrew Vos <[email protected]>wrote:
>>>
>>>> 1.0.0. What do you mean by state exactly?
>>>>
>>>>
>>>> On Sat, May 24, 2014 at 6:33 PM, Igor Motov <[email protected]> wrote:
>>>>
>>>>> Which version of elsticsearch are you using? Can you send me the 
>>>>> current cluster state?
>>>>>
>>>>> On Saturday, May 24, 2014 10:17:43 AM UTC-4, Andrew Vos wrote:
>>>>>>
>>>>>> A few days ago I started a snapshot, but instead of using a shared 
>>>>>> network I used the local filesystem. Because my root partition only had 
>>>>>> 8gb 
>>>>>> (and this is where I stored the snapshots) the partition got filled up 
>>>>>> and 
>>>>>> three of my seven elasticsearch boxes crashed almost instantly.
>>>>>>
>>>>>> I've since created a new cluster and let the data replicate over. The 
>>>>>> problem now is, I can't seem to cancel this snapshot!
>>>>>>
>>>>>> Looking at the snapshot:
>>>>>> *curl -XGET "localhost:9999/_snapshot/production_backup/_snapshot1"*
>>>>>> *{"error":"RemoteTransportException[[Smuggler][inet[/172.17.0.2 
>>>>>> <http://172.17.0.2>:9300]][cluster/snapshot/get]]; nested: 
>>>>>> SnapshotMissingException[[production_backup:_snapshot1] is missing]; 
>>>>>> nested: FileNotFoundException[/ebs/snapshot-backup/snapshot-_snapshot1 
>>>>>> (No 
>>>>>> such file or directory)]; ","status":404}%   *
>>>>>>
>>>>>> Starting a new snapshot:
>>>>>> *curl -XPUT 
>>>>>> "localhost:9999/_snapshot/production_backup/snapshot_1?wait_for_completion=false"*
>>>>>> *{"error":"RemoteTransportException[[Smuggler][inet[/172.17.0.2 
>>>>>> <http://172.17.0.2>:9300]][cluster/snapshot/create]]; nested: 
>>>>>> ConcurrentSnapshotExecutionException[[production_backup:snapshot_1] a 
>>>>>> snapshot is already running]; ","status":503}% *
>>>>>>
>>>>>> This just never completes:
>>>>>>
>>>>>> curl -XDELETE "localhost:9999/_snapshot/production_backup/snapshot_1"
>>>>>>
>>>>>>
>>>>>> Any idea how I can solve this?
>>>>>>
>>>>>  -- 
>>>>> You received this message because you are subscribed to a topic in the 
>>>>> Google Groups "elasticsearch" group.
>>>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>>>> topic/elasticsearch/rtffJxkKyzg/unsubscribe.
>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>> [email protected].
>>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>>> msgid/elasticsearch/41136f07-3afd-4452-87e4-a54f983db539%
>>>>> 40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/41136f07-3afd-4452-87e4-a54f983db539%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>  -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "elasticsearch" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/elasticsearch/rtffJxkKyzg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/9573402c-d7fe-419d-866f-cff1196fcfc4%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/9573402c-d7fe-419d-866f-cff1196fcfc4%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/ae997156-db75-4a2a-8a29-1435a50bb0f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to