Responses inline.
On Jul 7, 2014, at 10:54 PM, Tom Lanyon wrote:
> Hi Matthew,
>
> On Sunday, 6 July 2014 at 3:04, Matthew Von-Maszewski wrote:
>> Tom,
>>
>> Basho prides itself on quickly responding to all user queries. I have failed
>> that tradition in this case. Please accept my apologi
Hi Matthew,
On Sunday, 6 July 2014 at 3:04, Matthew Von-Maszewski wrote:
> Tom,
>
> Basho prides itself on quickly responding to all user queries. I have failed
> that tradition in this case. Please accept my apologies.
No problem; I appreciate you taking the time to look into our LOG.
>
> T
Tom,
Basho prides itself on quickly responding to all user queries. I have failed
that tradition in this case. Please accept my apologies.
The LOG data suggests leveldb is not stalling, especially not for 4 hours.
Therefore the problem is related to disk utilization.
You appear to have lar
Hot threads is included with 1.4.9. The leveldb source file
leveldb/util//hot_threads.cc is the key file.
The code helps throughput, but is not magical. "unresponsive for hours" is not
a known problem in the 1.4.x code base. Would you mind posting an aggregate
LOG file from a period when thi
Could someone please confirm whether 1.4.9 includes "Hot Threads" in leveldb?
The release notes have a link to it, but I couldn't find my way through the
rebar & git maze to be absolutely sure it is in 1.4.9 but not 1.4.8.
We're seeing nodes unresponsive for hours during large compactions and w
