Re: RepositoryMissingException when restoring into a new cluster
That was exactly what I was missing. I didn't create the repository named
"elasticsearch_logs" on cluster B. After I created it, the backup runs
smoothly.
Thanks, David!
On Wednesday, January 7, 2015 8:31:08 AM UTC+1, David Pilato wrote:
>
> Did you create the repository 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 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
> call that cluster b) from a snapshot generated from cluster a. When I run a
> restore request on cluster b, I get a 404. Doing a _status call on the
> snapshot, I get the same error:
>
> {"error":"RepositoryMissingException[[elasticsearch_logs]
> missing]","status":404}
>
>
> The new cluster is configured with the Azure plugin and the same settings for
> Azure. I guess the error is caused by the fact, that Elasticsearch generates
> some metadata about the snapshots and store them locally in a the _snapshot
> index and this index is not on the new cluster. The same error is happening
> if I delete the data dir on cluster a and try to restore cluster a from a
> snapshot.
>
>
> How would I deal with a situation like this?
>
> --
> 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 elasticsearc...@googlegroups.com .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/b5a0147c-cc38-4947-8530-0c66eb00fc2a%40googlegroups.com
>
> <https://groups.google.com/d/msgid/elasticsearch/b5a0147c-cc38-4947-8530-0c66eb00fc2a%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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2b1da7ff-9dd5-49ab-bd1f-34b38b1e0645%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
RepositoryMissingException when restoring into a new cluster
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
call that cluster b) from a snapshot generated from cluster a. When I run a
restore request on cluster b, I get a 404. Doing a _status call on the
snapshot, I get the same error:
{"error":"RepositoryMissingException[[elasticsearch_logs]
missing]","status":404}
The new cluster is configured with the Azure plugin and the same settings for
Azure. I guess the error is caused by the fact, that Elasticsearch generates
some metadata about the snapshots and store them locally in a the _snapshot
index and this index is not on the new cluster. The same error is happening if
I delete the data dir on cluster a and try to restore cluster a from a snapshot.
How would I deal with a situation like this?
--
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 visit
https://groups.google.com/d/msgid/elasticsearch/b5a0147c-cc38-4947-8530-0c66eb00fc2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Upgrade cluster from 0.90.11 to 1.1.1
Following the upgrade guide worked perfectly. Thank you very much for your help. On Saturday, April 26, 2014 11:09:11 AM UTC+2, David Pilato wrote: > > Important part is: > > 0.90.x > > 1.x > > Restart Upgrade > So you need to stop the whole cluster and restart. > > -- > David ;-) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > Le 26 avr. 2014 à 11:03, Srividhya Umashanker > > > a écrit : > > > http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html > > >= 0.90.7 > > 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 wait for it to synchronize. > > Let me know how it goes. > > On Saturday, April 26, 2014 12:50:37 PM UTC+5:30, Thomas Ardal wrote: >> >> 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 folder to 1.1.1. >> 4. start node 1 and wait for it to synchronize. >> 5. stop node 2. >> 6. install 1.1.1 on node 2. >> 7. copy data folder to 1.1.1. >> 8. start node 2 and wait for it to synchronize. >> >> I can live with downtime if not possible otherwise. >> > -- > 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 elasticsearc...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/5682b4a1-b978-44f3-a419-a6055358006f%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/5682b4a1-b978-44f3-a419-a6055358006f%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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4bc16a84-e2e2-4e68-8fd5-eca7daf0599b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Upgrade cluster from 0.90.11 to 1.1.1
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 folder to 1.1.1. 4. start node 1 and wait for it to synchronize. 5. stop node 2. 6. install 1.1.1 on node 2. 7. copy data folder to 1.1.1. 8. start node 2 and wait for it to synchronize. I can live with downtime if not possible otherwise. -- 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 visit https://groups.google.com/d/msgid/elasticsearch/26670af5-f4d5-4d11-859b-bdbbc08367f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Split brain problem on Azure
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 visit https://groups.google.com/d/msgid/elasticsearch/7e5eaf00-b943-4c64-aaad-a5ac78400ea3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Split brain problem on Azure
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 using the Azure plugin? -- 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 visit https://groups.google.com/d/msgid/elasticsearch/169394c1-6a8c-430e-a9c1-0286b1789fce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: There were no results because no indices were found that match your selected time span
Okay, thanks! On Tuesday, January 28, 2014 8:53:27 PM UTC+1, David Pilato wrote: > > Should work from 0.90.9. > > -- > *David Pilato* | *Technical Advocate* | *Elasticsearch.com* > @dadoonet <https://twitter.com/dadoonet> | > @elasticsearchfr<https://twitter.com/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 Marvel only support the most recent versions of ES? > > On Tuesday, January 28, 2014 8:43:26 PM UTC+1, David Pilato wrote: >> >> 0.90.1? >> You 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 Jetty plugin to force https and basic authentication, but are >> accessing Marvel from localhost through http. My browser asks me for >> credentials when opening the Marvel url, so it could be caused by 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" in the top of the page. >>> >>> If I understand the documentation, Marvel automatically collects >>> statistics from all indexes on the node. What am I doing wrong? >>> >> -- >> 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 elasticsearc...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/7255ee52-5101-4942-8abd-b29642035237%40googlegroups.com >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> -- > 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 elasticsearc...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/8bee9ba2-d0bf-42c3-b8ac-2c45707b9f96%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 visit https://groups.google.com/d/msgid/elasticsearch/c2e396aa-7fcb-4257-ba10-c5b89827f662%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: There were no results because no indices were found that match your selected time span
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 Marvel only support the most recent versions of ES? On Tuesday, January 28, 2014 8:43:26 PM UTC+1, David Pilato wrote: > > 0.90.1? > You 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 Jetty plugin to force https and basic authentication, but are > accessing Marvel from localhost through http. My browser asks me for > credentials when opening the Marvel url, so it could be caused by 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" in the top of the page. >> >> If I understand the documentation, Marvel automatically collects >> statistics from all indexes on the node. What am I doing wrong? >> > -- > 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 elasticsearc...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/7255ee52-5101-4942-8abd-b29642035237%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 visit https://groups.google.com/d/msgid/elasticsearch/8bee9ba2-d0bf-42c3-b8ac-2c45707b9f96%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: There were no results because no indices were found that match your selected time span
As bonus info I'm running Elasticsearch 0.90.1 on windows server 2012. I'm using the Jetty plugin to force https and basic authentication, but are accessing Marvel from localhost through http. My browser asks me for credentials when opening the Marvel url, so it could be caused by 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" in the top of the page. > > If I understand the documentation, Marvel automatically collects > statistics from all indexes on the node. What am I doing wrong? > -- 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 visit https://groups.google.com/d/msgid/elasticsearch/7255ee52-5101-4942-8abd-b29642035237%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
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. What am I doing wrong? -- 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 visit https://groups.google.com/d/msgid/elasticsearch/454e6e01-de1a-4a23-b270-16bf90273c47%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
