You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by GitBox <gi...@apache.org> on 2020/05/29 11:13:58 UTC

[GitHub] [hbase] bsglz edited a comment on pull request #1799: HBASE-24455 Correct the doc of "On the number of column families"

bsglz edited a comment on pull request #1799:
URL: https://github.com/apache/hbase/pull/1799#issuecomment-635916351


   Sounds reasonable, WDYT changed to this:
   _HBase currently does not do well with anything above two or three column families so keep the number of column families in your schema low.
   Currently, flushing is done on a per Region basis so if one column family is carrying the bulk of the data bringing on flushes, the adjacent families will also be flushed even though the amount of data they carry is small.
   When many column families exist the flushing interaction can make for a bunch of needless i/o (To be addressed by changing flushing to work on a per column family basis).
   **In addition, compactions triggered at table/region level will happen per store too.**_


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org