50 Region Servers for 100 TB such that each RS serves 10 regions (500 regions).
At this stage, we haven't evaluated the impact on query latency when running with fewer regions, for ex., 50 RS and 250 regions. On Wed, Sep 24, 2014 at 11:50 AM, James Taylor <jamestay...@apache.org> wrote: > Would you be able to talk about your use case a bit and explain why you'd > need this to be higher? > Thanks, > James > > > On Wednesday, September 24, 2014, Krishna <research...@gmail.com> wrote: > >> Thanks... any plans of raising number of bytes for salt value? >> >> >> On Wed, Sep 24, 2014 at 10:22 AM, James Taylor <jamestay...@apache.org> >> wrote: >> >>> The salt byte is the first byte in your row key and that's the max >>> value for a byte (i.e. it'll be 0-255). >>> >>> On Wed, Sep 24, 2014 at 10:12 AM, Krishna <research...@gmail.com> wrote: >>> > Hi, >>> > >>> > According to Phoenix documentation >>> > >>> >> "Phoenix provides a way to transparently salt the row key with a >>> salting >>> >> byte for a particular table. You need to specify this in table >>> creation time >>> >> by specifying a table property “SALT_BUCKETS” with a value from 1 to >>> 256" >>> > >>> > >>> > Is 256 the max value that SALT_BUCKETS can take? If yes, could someone >>> > explain the reason for this upper bound? >>> > >>> > Krishna >>> > >>> >> >>
