Hi Max,
Thanks for the reply. We recently started 6 DB servers each 15 GB Disk and
15 GB ram, the DB servers were able to store slightly more data maybe
about 9 GB in total across all the machines and then it crashed with the
same messages in the log :
2017-01-10T13:04:25Z [1] INFO (expected layout: size (4 bytes), crc (4
bytes), type and tick (8 bytes), payload following)
2017-01-10T13:04:25Z [1] INFO 0x0000000000C97F88: E4 00 00 00 00 00 00 00
B1 22 1E 02 00 00 00 1E ........ ."......
2017-01-10T13:04:25Z [1] INFO 0x0000000000C97F98: 76 FA 1D 02 00 00 00 00
0B CC 07 31 77 31 30 34 v....... ...1w104
2017-01-10T13:04:25Z [1] INFO 0x0000000000C97FA8: 2E 35 31 2E 32 30 39 2E
32 35 31 5F 39 62 34 31 .51.209. 251_9b41
2017-01-10T13:04:25Z [1] INFO 0x0000000000C97FB8: 65 37 61 30 62 32 31 65
65 39 62 63 39 39 66 37 e7a0b21e e9bc99f7
2017-01-10T13:04:25Z [1] INFO 0x0000000000C97FC8: 66 32 61 36 32 61 36 33
31 36 65 39 39 33 36 65 f2a62a63 16e9936e
2017-01-10T13:04:25Z [1] INFO 0x0000000000C97FD8: 30 36 66 37 33 F3 0F 4E
2F 00 00 00 00 00 34 58 06f73..N /.....4X
2017-01-10T13:04:25Z [1] INFO 0x0000000000C97FE8: 49 70 41 64 64 72 65 73
73 2F 31 30 34 2E 35 31 IpAddres s/104.51
2017-01-10T13:04:25Z [1] INFO 0x0000000000C97FF8: 2E 32 30 39 2E 32 35 31
35 74 50 68 79 4C 6F 63 .209.251 5tPhyLoc
2017-01-10T13:04:25Z [1] INFO 0x0000000000C98008: 61 74 69 6F 6E 2F 39 62
34 31 65 37 61 30 62 32 ation/9b 41e7a0b2
2017-01-10T13:04:25Z [1] INFO 0x0000000000C98018: 31 65 65 39 62 63 39 39
66 37 66 32 61 36 32 61 1ee9bc99 f7f2a62a
2017-01-10T13:04:25Z [1] INFO 0x0000000000C98028: 36 33 31 36 65 39 39 33
36 65 30 36 66 37 32 4B 6316e993 6e06f72K
2017-01-10T13:04:25Z [1] INFO 0x0000000000C98038: 5F 55 57 66 76 74 73 32
2D 2D 4D 4A 43 6F 6E 66 _UWfvts2 --MJConf
2017-01-10T13:04:25Z [1] INFO 0x0000000000C98048: 69 64 65 6E 63 65 1B 28
F2 24 E9 9A C9 BF 3F 42 idence.( .$....?B
2017-01-10T13:04:25Z [1] INFO 0x0000000000C98058: 54 53 4A 32 30 31 36 2D
31 32 2D 32 30 A3 B7 46 TSJ2016- 12-20..F
2017-01-10T13:04:25Z [1] INFO 0x0000000000C98068: 3C 03 96 60 00 00 00 00
20 00 00 00 56 86 7C 8E <..`.... ...V.|.
2017-01-10T13:04:25Z [1] INFO 0x0000000000C98078: B2 22 1E 02 00 00 00 19
."......
2017-01-10T13:04:25Z [1] INFO data directly following this marker looks ok
so repairing the marker manually may recover it...
2017-01-10T13:04:25Z [1] INFO to truncate the file at this marker, please
restart the server with the parameter '--wal.ignore-logfile-errors true' if
the error happening during WAL recovery, or with parameter
'--database.ignore-datafile-errors true' if it happened after WAL recovery
2017-01-10T13:04:25Z [1] ERROR datafile
'/var/lib/arangodb3/journals/logfile-35003210.db' is corrupt
2017-01-10T13:04:25Z [1] ERROR unable to open logfile
'/var/lib/arangodb3/journals/logfile-35003210.db': corrupted datafile
2017-01-10T13:04:25Z [1] FATAL could not inspect WAL logfiles: corrupted
datafile
Please can you suggest us the best option to avoid this situation. Are
there any options to mount Amazon EBS as external volumes and make the
Docker
containers store the persistent DB data in the EBS.
Thanks,
Praveen
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
