Hmm,.. I don't know if this helped, but after about 30 minutes ES got
started and it works now...
My system doesn't have /etc/init.d/ntp file, so I doubt the command was the
reason why it's started.
I'm actualy very surprised it took so much time. Could something be done
about this? I also noticed that there are about 1700 files for node 0 of
the index. Other nodes have something around 200 files.
I guess this is wrong, but I'm not sure about this.
Could it be fixed somehow? Or is this wrong at all?
Anyway, if someone had such problems, please share. Any information is
On Saturday, June 30, 2012 10:41:57 PM UTC-4, Pedro Alves wrote:
Who cares as long as it works?
On Sun Jul 1 03:32:13 2012, Eugene Strokin wrote:
Thank you Pedro,
but what does it mean really?
How it helps?
On Saturday, June 30, 2012 10:30:00 PM UTC-4, Pedro Alves wrote:
/etc/init.d/ntp stop; date; date `date +"%m%d%H%M%C%y.%S"`; date;
Stupid leap second
On Sun Jul 1 03:24:01 2012, Eugene Strokin wrote:
> Suddenly, ES start being unresponsive from time to time.
> I've decided to restart it.
> But it stack at initializing:
> [2012-06-30 21:01:49,080][INFO ][bootstrap ] max_open_files
> [2012-06-30 21:01:49,089][INFO ][node ] [Piledriver]
> initializing ...
> [2012-06-30 21:01:49,093][INFO ][plugins ] [Piledriver] loaded ,
> sites 
> I'm waiting for 20 minutes for initializing complete. This is
> relatively small index (around 1 GB). It shouldn't take that
> I see that Java process takes some CPU, but not 100% (20-40 % in
> What it could be?
> Should I start to upload my back ups?
> Thank you