So if you kill a joining node, it will remain as a Fat Client (as of 0.7.x) in
gossip. That is innocuous on its own. However if a node was decommissioned
while that was joining, then the lingering Fat Client will also gossip about
the node that was decommissioned. Then it will try to hint for
I would assume it's because it thinks some node is down and is
creating hints for it.
On Thu, Aug 18, 2011 at 6:31 PM, Jeremy Hanna
wrote:
> We're trying to bootstrap some new nodes and it appears when adding a new
> node that there is a lot of logging on hints being flushed and compacted.
> I
We're trying to bootstrap some new nodes and it appears when adding a new node
that there is a lot of logging on hints being flushed and compacted. It's been
taking about 75 minutes thus far to bootstrap for only about 10 GB of data.
It's ballooned up to over 40 GB on the new node. I do 'ls -
