hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: [from EMC Isilon] -- pls. review "Why HBase on EMC Isilon" post
Date Thu, 01 Sep 2016 19:30:56 GMT
On Thu, Sep 1, 2016 at 1:52 AM, Chernov, Arseny <Arseny.Chernov@emc.com>

> Dear colleagues at User@HBase ,
> I really value your time and thank you for attention. I understand that,
> without context setting, my mail carries a substantial risk to trigger a
> huge off-top. This is not my intention at all.
> So, brief context is: we at EMC Isilon see strong uptake of HBase in
> mid-market and enterprise datacenters, where sustained practices of ITIL,
> compliance, legacy architectures and cost control , -- oftentimes are not
> correlating well with true “Big Table” web-scale concepts of this brilliant
> database. We see emergence of small, order of 100-s of TB-s, virtualised
> HBase deployments, in different pockets of enterprise, as well.
> I humbly ask you to review and share your feedback (1x1 or in this forum)
> your PoV-s on “Why HBase on Isilon” blogpost that I’ve just published:
> Why HBase on EMC Isilon – Top 5 Reasons http://bit.ly/2bSmKgc
> I’m very keen to learn more from this respected community, as well as
> possibly answer your questions about EMC Isilon and share (to extent of
> what could be shared) what we see.

Thanks for pinging the list Arseny.

Does HBase just-work on Isilon? Did you have to make any changes? It'd be
sweet if you or your multi-PB customers could write up some on how the
deploys are done, their experience (e.g. Dima's question above), and what
needs improving running hbase on isilon.

Beyond, given Isilon is a scalable posix-compatible FS with some nice
features, HBase is only making use of a severe subset of the facility
available. It would be fun to figure a more applicable datastore
architecture given what they underlying FS is capable of.


> --
> Arseny Chernov
> 陈毅誠

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message