Open JulianKingman opened 8 years ago
If so, I liked to know the error thrown by Kadira?
Unfortunately, there are no error codes other than what I gave, which I admit makes it very difficult to debug. @brugnara, do you have any more info on this error?
@JulianKingman @arunoda I'm getting this too, but it is not the cause of kadira. I'm indexing documents to Elasticsearch. Maybe this behaviour is caused by HTTP
module somehow?
Thanks @bompi88, is there an open issue for this, or where would you open an issue? With no error codes, I'm at quite a loss of where to continue.
@JulianKingman I found out that my docker machine only had 1g memory located, and I was running 3 containers in it. I increased the elastic search containers memory, together setting ES_HEAP_SIZE to 2g and the container memory to 3g with the -m
switch. I haven't had the issue since. Looks like Elasticsearch did not have resources enough to process all the indexing requests while indexing about 22k documents, and that somehow triggered this issue. Could it be a memory related problem?
Definitely could be, I'll try increasing that for starters.
Hi everybody.
I am unable to reproduce but I still have this issue on production with the newest kadira module (meteorhacks:kadira@2.20.1).
I have in my logs some of this error:
Here you can see my four containers. The first two are with meteord + kadira. third and fourth are mongo and teamspeak containers and as you can see from the uptime, I have no issues with those.
If you need more details, feel free to ask. Thanks for your time and support.
How much memory do they have? Mine was only 512mb, so I'm thinking lack of memory is a definite possibility, although I'm not sure it was using the full amount...
Per this issue: https://github.com/meteorhacks/meteord/issues/58
Running Kadira in a MeteorD container appears to cause a crash after a period of time, with no error besides something like this:
meteor-1 | 2016-02-09T12:01:20.921668753Z /opt/meteord/run_app.sh: line 44: 24 Killed node main.js