Hello, I'm looking for some information on hbase's architecture (out of pure interest), which i wasn't able to find anything about it on the Hbase site (including the architecture description).
Specifically, I am curious how writes/mutations are distributed amongst the servers, and whether this is different when using an interface like Thrift. Is a server located for each mutateRow () operations "asked for" at the master server, or is that cached at some level ? If not, how is that problem solved that a client only connects to the master server but actually needs to talk to one of the slave servers ? Or is the master server a single weak spot that could introduce scalability problems on large (huge) scale ? Thanks in advance for any responses! Regards, Leon Mergen
