[
https://issues.apache.org/jira/browse/AMBARI-11290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554618#comment-14554618
]
Nick Dimiduk commented on AMBARI-11290:
---------------------------------------
This might be problematic because the salt cardinality cannot be changed after
the table is created, and the sequence table cannot be dropped after other
schema have started using the sequences it generates.
I think the better solution is to decouple salt cardinality from number of
regions. [~jamestaylor] probably has an opinion on this. James, do you do
anything different with the sequence table on small clusters?
> Avg Load for HBase is 261 regions per RS for a fresh one node cluster
> ---------------------------------------------------------------------
>
> Key: AMBARI-11290
> URL: https://issues.apache.org/jira/browse/AMBARI-11290
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 2.1.0
>
>
> This happens because newer version of Phoenix sets salBuckets for sequence
> table to 256 creating 256 regions for salting by default.
> We can add the above config to Ambari's computed values – anything smaller
> than 10 RS's should use a value of $numRs * 5. Something like this. It could
> be a hassle for folks who start small and add nodes; they'll need to split
> the table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
