HW1
March 15, 2015, 10:22pm
1
Hello,
I am facing a problem with restarting my event-store on a small amazon ec2 instance.
Note : My event database is very small, i am talking of a few hundreds events on only one aggregate.
I am having this content in log files :
[PID:06356:006 2015.03.15 22:19:10.035 TRACE TFChunk ] Verifying hash for TFChunk ‘/home/eventStore/db/chunk-000000.000000’…
Note : Very strange to see log talking of 109386 records when my database is so small.
The problem is that this process is never ending so my database is never available.
How can i handle this case ? Is there a way to quickly repair a get-event-store database ?
Thank you in advance.
you have statistics being written in your database as well. By default
$statistics-ip:port
You can set a limit on the stream for how many to keep and even turn
As for it never ending it looks in that log to be making progress.
How do you determine its never ending? Also what are you running on
HW1
March 15, 2015, 11:24pm
3
Uhm cool i’ll check this statistic setting.
I determine its never ending because my event-store web-ui is never reachable.
For now i see those “ReadIndex Rebuilding” lines in logs so i deducted that this process is responsible.
Thank you for the quick reply !
when it finishes the ui becomes available.
To be fair on my laptop this generally takes about 1 second
HW1
March 16, 2015, 12:13am
5
Yeah on my macbook pro its lightning fast.
Maybe related to ec2.small instance with amazon ami. Gonna try something bigger.
Thank you very much for your help.
HW1
March 18, 2015, 10:42am
6
Well i am still stucked trying to have a stable getEventStore on ec2.small instance.
After multiple instance freeze i discovered this with “iotop” :
TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
23241 be/4 john 170.18 K/s 0.00 B/s 0.00 % 94.69 % clusternode --config=/home/eventStore/eventStore.yaml
``
The issue here may be related to this never ending task of “ReadIndex Rebuilding” (never ending = when it hit 100% then it start over at 1% with the next file…forever) :
Does anyone know what i could try to stop this ?
I tried 10 times to stop and restart but the result is always the same.
[PID:22884:295 2015.03.18 10:33:34.271 DEBUG IndexCommitter ] ReadIndex Rebuilding: processed 35620 records (18.5%).
``
When you restart it starts from beginning.
This is VERY VERY slow though. What size are your events you have written?
It will come up eventually (its still processing) and it looks like
