> On Feb 4, 2015, at 5:55 AM, fitcs <john.forr...@neotechnology.com> wrote: > > I suspect you are seeing a false positive from the consistency check run > during an incremental. There is an option to not do the check ( -verify > false ) and the do a full consistency check on the backup store. > > Full consistency check tuning and more details of these options are covered > in Mark's blog: > > ``` > http://www.markhneedham.com/blog/2014/01/22/neo4j-backup-store-copy-and-consistency-check/ > ```
Nice, I’ll take a look at that, thanks!
> If you could provide the error/trace from your experience it will help with
> the repro. It would also be good to know if it is not a false positive i.e.
> if the full check identifies an issue.
Ok, here’s mine:
> $ /usr/bin/neo4j-backup -host localhost -to /mnt/neo4j_backups/dump
> Performing backup from '127.0.0.1:6362'
> Transactions applied
> Exception in thread "main" org.neo4j.consistency.ConsistencyCheckingError:
> Inconsistencies in transaction:
> Start[3,xid=GlobalId[NEOKERNL|723968400398398807|26298|540], BranchId[
> 52 49 52 49 52 49 ],master=540,me=540,time=2015-01-29
> 20:46:55.441+0000/1422564415441,lastCommittedTxWhenTransactionStarted=99274]
> 1PC[3, txId=99275, 2015-01-29 20:46:55.443+0000/1422564415443]
> ConsistencySummaryStatistics{
> Number of errors: 1
> Number of warnings: 0
> Number of inconsistent RELATIONSHIP records: 1
> }
> at
> org.neo4j.consistency.checking.incremental.intercept.CheckingTransactionInterceptor.complete(CheckingTransactionInterceptor.java:181)
> at
> org.neo4j.kernel.impl.transaction.xaframework.LogEntryVisitorAdapter.apply(LogEntryVisitorAdapter.java:62)
> at
> org.neo4j.kernel.impl.transaction.xaframework.LogEntryVisitorAdapter.apply(LogEntryVisitorAdapter.java:28)
> at
> org.neo4j.kernel.impl.nioneo.xa.command.LogFilter.endLog(LogFilter.java:87)
> at
> org.neo4j.kernel.impl.transaction.xaframework.XaLogicalLog.applyTransaction(XaLogicalLog.java:1121)
> at
> org.neo4j.kernel.impl.transaction.xaframework.XaResourceManager.applyCommittedTransaction(XaResourceManager.java:866)
> at
> org.neo4j.kernel.impl.transaction.xaframework.XaDataSource.applyCommittedTransaction(XaDataSource.java:246)
> at
> org.neo4j.com.ServerUtil.applyReceivedTransactions(ServerUtil.java:461)
> at org.neo4j.backup.BackupService.unpackResponse(BackupService.java:423)
> at
> org.neo4j.backup.BackupService.incrementalWithContext(BackupService.java:330)
> at
> org.neo4j.backup.BackupService.doIncrementalBackup(BackupService.java:269)
> at
> org.neo4j.backup.BackupService.doIncrementalBackup(BackupService.java:222)
> at
> org.neo4j.backup.BackupService.doIncrementalBackupOrFallbackToFull(BackupService.java:243)
> at org.neo4j.backup.BackupTool.doBackup(BackupTool.java:225)
> at org.neo4j.backup.BackupTool.executeBackup(BackupTool.java:189)
> at org.neo4j.backup.BackupTool.runBackup(BackupTool.java:180)
> at org.neo4j.backup.BackupTool.run(BackupTool.java:134)
> at org.neo4j.backup.BackupTool.main(BackupTool.java:90)
> $ java -cp '/var/lib/neo4j/lib/*:/var/lib/neo4j/system/lib/*'
> org.neo4j.consistency.ConsistencyCheckTool /mnt/neo4j_backups/dump
> Full consistency check
> .................... 10%
> .................... 20%
> .................... 30%
> .................... 40%
> .................... 50%
> .................... 60%
> .................... 70%
> .................... 80%
> .................... 90%
> .................... 100%
So it looks like that worked. I’m doing another run with -verify false now to
see what happens.
> $ /usr/bin/neo4j-backup -host localhost -to /mnt/neo4j_backups/dump -verify
> false
> Performing backup from '127.0.0.1:6362'
> Transactions applied
> ...2015-02-05 21:09:56.748+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 214ms.
> ..........2015-02-05 21:12:54.473+0000 WARN [o.n.k.EmbeddedGraphDatabase]:
> GC Monitor: Application threads blocked for 588ms.
> .2015-02-05 21:13:00.097+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 819ms.
> ...... 20000
> 2015-02-05 21:14:23.847+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC Monitor:
> Application threads blocked for 203ms.
> ...2015-02-05 21:15:06.334+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 202ms.
> .2015-02-05 21:15:24.607+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 202ms.
> ...2015-02-05 21:15:57.168+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 271ms.
> ........2015-02-05 21:17:54.484+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 201ms.
> .2015-02-05 21:18:03.058+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 202ms.
> 2015-02-05 21:18:14.233+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC Monitor:
> Application threads blocked for 212ms.
> ...
> . 40000
> .....2015-02-05 21:21:32.577+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 203ms.
> ....2015-02-05 21:22:40.128+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 217ms.
> 2015-02-05 21:23:22.158+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC Monitor:
> Application threads blocked for 555ms.
> .2015-02-05 21:24:16.086+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 208ms.
> ..2015-02-05 21:25:57.772+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 204ms.
> .2015-02-05 21:26:41.331+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 202ms.
> ...2015-02-05 21:29:53.908+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 401ms.
> 2015-02-05 21:30:06.401+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC Monitor:
> Application threads blocked for 243ms.
> .2015-02-05 21:30:25.375+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC
> Monitor: Application threads blocked for 202ms.
> ... 60000
> 2015-02-05 21:32:09.029+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC Monitor:
> Application threads blocked for 654ms.
> 2015-02-05 21:32:13.674+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC Monitor:
> Application threads blocked for 540ms.
> 2015-02-05 21:32:28.375+0000 WARN [o.n.k.EmbeddedGraphDatabase]: GC Monitor:
> Application threads blocked for 204ms.
> …………
> done
> Done
> $ java -cp '/var/lib/neo4j/lib/*:/var/lib/neo4j/system/lib/*'
> org.neo4j.consistency.ConsistencyCheckTool /mnt/neo4j_backups/dump
> Full consistency check
> .................... 10%
> .................... 20%
> .................... 30%
> .................... 40%
> .................... 50%
> .................... 60%
> .................... 70%
> .................... 80%
> .................... 90%
> .................... 100%
FWIW, the failed backup run failed nearly immediately, whereas the one that
played back 60k+ transactions? took about 15 minutes to complete, so I think
it’s failing on the very first transaction it’s trying to play back?
Thanks!
-Jeremy
--
You received this message because you are subscribed to the Google Groups
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
