A colleague of mine has a question about scalability and connections to HBase.
We’d like to use the label-based controls for our content. Those labels are tied to users and users are specified on connections (not when getting the HBase table, which is really too bad because if they were I wouldn’t be writing to y’all.) Chances are we’re not going to be able to use the built-in connection pooling because of this: every user will require a connection of their own, because every user will be associated with different labels. Assuming we create unshared HConnections when each user wants to perform some operation and destroy that connection at the end of every request, how scalable is this? (I’m assuming “not at all”, but I’d like confirmation.) Has anyone run tests to see how many connections per minute are feasible? I pointed out to this colleague that one of the first things you learn when using a database is to pool (and reuse) connections. That connections are tied to users, which are then tied to labels, causes us to reconsider these lessons. Thanks in advance. -j
