y on cluster B?
> How?
>
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
> Le 7 janv. 2015 à 08:19, Thomas Ardal >
> a écrit :
>
> I'm using the snapshot/restore feature of Elasticsearch, together with the
> Azure plugin to backup s
I'm using the snapshot/restore feature of Elasticsearch, together with the
Azure plugin to backup snapshots to Azure blob storage. Everything works
when doing snapshots from a cluster and restoring to the same cluster. Now
I'm in a situation where I want to restore an entirely new cluster (let's
gt;
> 0.90.x
>
> Rolling Upgrade
>
> 1.x
>
> 1.x
>
> Rolling Upgrade
> I guess the upgrade will upgrade to latest lucene automatically.
> 1. stop node 1.
> 2. install 1.1.1 on node 1.
> *[NOT REQUIRED] **3. copy data folder to 1.1.1.*
> 4. start node 1 and wai
I'm running a two-node cluster with Elasticsearch 0.90.11. I want to
upgrade to the newest version (1.1.1), but I'm not entirely sure on how to
do it. 0.90.11 is based on Lucene 4.6.1 and 1.1.1 on Lucene 4.7.2. Can I do
the following:
1. stop node 1.
2. install 1.1.1 on node 1.
3. copy data fol
Ok. Also using the zen.* keys?
--
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web vi
I'm experiencing split brain problem on my Elasticsearch cluster on Azure,
consisting of two nodes. I've read about the zen.ping.timeout
and discovery.zen.minimum_master_nodes settings, but I guess that I can't
use those settings, when using the Azure plugin. Any ideas for avoiding
split brain
m/elasticsearchfr>
>
>
> Le 28 janvier 2014 at 20:51:14, Thomas Ardal
> (thoma...@gmail.com)
> a écrit:
>
> I know and that's the plan. But with 1.0.0 right around the corner and a
> lot of data to migrate, I'll probably wait for that one.
>
> Does Marve
ou should update to 0.90.10.
>
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
> Le 28 janv. 2014 à 20:11, Thomas Ardal >
> a écrit :
>
> As bonus info I'm running Elasticsearch 0.90.1 on windows server 2012. I'm
> using the
the basic
authentication setup. Or?
On Tuesday, January 28, 2014 8:01:21 PM UTC+1, Thomas Ardal wrote:
>
> When trying out Marvel on my Elasticsearch installation, I get the error
> "There were no results because no indices were found that match your
> selected time span"
When trying out Marvel on my Elasticsearch installation, I get the error
"There were no results because no indices were found that match your
selected time span" in the top of the page.
If I understand the documentation, Marvel automatically collects statistics
from all indexes on the node. Wha
10 matches
Mail list logo
