Details
Critical Description
kturner writes:
I was running a Fluo test with 1.8.0-SNAP on my workstation. My Fluo table had a ton of tablets. I was seeing terrible performance. I started looking at the tserver and noticed it was always calling hsync. I tracked down the problem to the fact that when minc start and stop events are written to the log they are always written w/ sync level. My poor little tserver was constantly minor compacting (probably had around 600 tablets that were all being written to).
I changed the test config to create like 15 tablets and the performance was much better. All cores were 100% utilized, which was not the case when hsync was always called.
Attachments
Attachments
Issue Links
- relates to
-
ACCUMULO-4146 Per-durability write-ahead logs
-
- Open
-
- links to
