Hi Alexander,
Any updates on this?
Thanks,
Rohit
On Sat, Jun 21, 2014 at 9:51 AM, Rohit Jaiswal rohit.jais...@gmail.com
wrote:
Hi Alexander,
I sent you stack trace for both the problems.
1. The InvalidAliasNameException was supposedly fixed in version
/elasticsearch/issues/4502
Maybe you run into that?
On Sun, Jun 22, 2014 at 10:18 PM, Rohit Jaiswal rohit.jais...@gmail.com
wrote:
Yes, it did when we restarted the node while trying to reproduce this
problem. We also were able to access the data using the Scan search api
after restarting
To further assist in this, here are our gateway settings -
gateway:
recover_after_nodes: 20
recover_after_time: 5m
expected_nodes: 20
Thanks,
Rohit
On Mon, Jun 23, 2014 at 1:02 PM, Rohit Jaiswal rohit.jais...@gmail.com
wrote:
Hi Boaz,
How can we fix
...
Cheers,
Boaz
On Monday, June 16, 2014 10:26:06 PM UTC+2, Rohit Jaiswal wrote:
Hi Boaz,
We are using 0.90.2 and run into this issue. As i
understand, one option is to upgrade to 0.90.3. If we continue using 0.90.2
and use (increase) retry_on_conflict, we will not see the problem
/elasticsearch/issues/3448
Thanks,
Rohit
On Fri, Jun 20, 2014 at 6:52 AM, Rohit Jaiswal rohit.jais...@gmail.com
wrote:
Hi Alexander,
Here is the stack trace for the NullpointerException -
[23:24:38,929][DEBUG][action.bulk ] [Rasputin, Mikhail
NullPointerException in your first post, which is not
contained in the stacktrace, so it seems, that one is still missing.
Also, please retry with a newer version of Elasticsearch.
--Alex
On Thu, Jun 19, 2014 at 5:13 AM, Rohit Jaiswal rohit.jais...@gmail.com
wrote:
Hi Alexander
Hi Alexander,
We sent you the stack trace. Can you please enlighten us on
this?
Thanks,
Rohit
On Mon, Jun 16, 2014 at 10:25 AM, Rohit Jaiswal rohit.jais...@gmail.com
wrote:
Hi Alexander,
Thanks for your reply. We plan to upgrade in the
long run
, so it should
have been logged into the elasticsearch logfile as well). Also, you should
really upgrade if possible, as releases after 0.90.2 have seen many many
improvements.
--Alex
On Mon, Jun 9, 2014 at 4:15 AM, Rohit Jaiswal rohit.jais...@gmail.com
wrote:
Hello Everyone
Hello Everyone,
We lost data after restarting Elasticsearch
cluster. Restarting is a part of deploying our software stack.
We have a 20-node cluster running 0.90.2 and we
have Splunk configured to index ES logs.