Ted, one thing to point out though is that in the scenario I described, the same thing would happen if you didn't call start-hbase.sh. The start/stop behaviors I described are independent of each other so you can stop the cluster remotely even without the second master running.
This is because stopping the master is done by starting a VM and running oahh.master.HMaster stop with the remote configs. This seems to happen regardless of whether there's a match on a local pid file with a local master process. On Wed, Mar 2, 2011 at 8:57 PM, Stack <[email protected]> wrote: > On Wed, Mar 2, 2011 at 5:23 PM, Bill Graham <[email protected]> wrote: >> So the question is, is this a bug or a feature? If it's a feature it >> seems like an incredibly dangerous one. Once our live cluster is >> running, those configs will also be needed on the client so really bad >> things could happen by mistake. >> > > One time it might have been thought a 'feature' but now its a bug I'd > say given the above. I opened > https://issues.apache.org/jira/browse/HBASE-3590 using this thread as > context. > > St.Ack >
