Hi Josh, Another potentially useful config setting for anyone using KFS is > > Kfs.Broker.Flush = true
I think the variance you observed here must have just been a coincidence. This property is no longer used by the KFS broker. daily maintenance window for the database. I've finally figured out > that a safe sequence for shutdown is: > > 1) Kill all ThriftBrokers and any other clients (eg, load data > infile's via ./bin/hypertable) which might be interacting with the > RangeServers (especially inserts) > 1a) double check that the RangeServers are idle / not busy finishing > anything heavyweight like compactions or what have you > 2) Run "shutdown;" in the hypertable shell and verify that all of the > RangeServers go down > 3) Run ./bin/stop-servers.sh on the master and verify that > Hypertable.Master and Hyperspace.Master are down > 4) Kill all other running binaries, probably just the DFS Brokers (in > our case it's kosmosBroker) Since you're using KFS, you should be able to stop and start the cluster with just: cap stop cap start In other words, you should be able to stop Hypertable by just killing all the binaries. Have you observed that this does not work? - Doug --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hypertable-dev?hl=en -~----------~----~----~----~------~----~------~--~---
