On Fri, Feb 20, 2015 at 2:33 PM, Denis <[email protected]> wrote: > > Did you have walogs laying around when you upgraded? > > In 1.4-cluster (and first time in 1.6-cluster) I had walogs enabled > for data tables and disabled for index tables. > > There was a bug in 1.4, if a tablet had empty walog there were some > startup issues (tablet remains offline or something like this), and it > happened often with index tables (hmm, the same tables I have this > problem). > > So, in 1.4-cluster I disabled walog and ran full reindex periodically. > After running 1.6-cluster some time I enabled walogs for all tables as > the new cluster have less reliable hardware, which reboots from time > to time. > > So just to confirm, you have seen this issue appear while walogs are enabled for all tables, yes?
Any chance you can share your code that writes across several BatchWriters? -- Sean
