No. There isn't. But I want to figure out how to configure that type of cluster in the case if there is particular reason. How facebook can handle such a huge amount of ops without federation? I don't think that they just have one namenode server and one standby namenode server. It isn't possible. I am sure that they use federation.
On Fri, Aug 19, 2016 at 10:08 PM, Vladimir Rodionov <[email protected]> wrote: > >> I am not sure how to do it but I have to configure federated cluster > with > >> hbase to store huge amount of messages (client to client) (40% writes, > 60% > >> reads). > > Any particular reason for federated cluster? How huge is huge amount and > what is the message size? > > -Vladimir > > On Fri, Aug 19, 2016 at 11:57 AM, Dima Spivak <[email protected]> > wrote: > > > As far as I know, HBase doesn't support spreading tables across > namespaces; > > you'd have to point it at one namenode at a time. I've heard of people > > trying to run multiple HBase instances in order to get access to all > their > > HDFS data, but it doesn't tend to be much fun. > > > > -Dima > > > > On Fri, Aug 19, 2016 at 11:51 AM, Alexandr Porunov < > > [email protected]> wrote: > > > > > Hello, > > > > > > I am not sure how to do it but I have to configure federated cluster > with > > > hbase to store huge amount of messages (client to client) (40% writes, > > 60% > > > reads). Does somebody have any idea or examples how to configure it? > > > > > > Of course we can configure hdfs in a federated mode but as for me it > > isn't > > > suitable for hbase. If we want to save message from client 1 to client > 2 > > in > > > the hbase cluster then how hbase know in which namespace it have to > save > > > it? Which namenode will be responsible for that message? How we can > read > > > client messages? > > > > > > Give me any ideas, please > > > > > > Sincerely, > > > Alexandr > > > > > > > > > > > -- > > -Dima > > >
