Josh, thanks for reading and sharing feedback. Agreed with starting simple and
measuring inputs that are high-signal; that’s a good place to begin.
To the challenge of building consensus, point taken + agreed. Perhaps the
distinction is between producing something that’s “useful” vs. something t
I have created a sub-task - CASSANDRA-14783. Could we get some feedback before
we begin implementing anything?
Dinesh
On Thursday, September 20, 2018, 11:22:33 PM PDT, Dinesh Joshi
wrote:
I have updated the doc with a short paragraph providing the clarification.
Sankalp's suggestion
One thing that's really, really bothered me for a while is how we default
to 256 tokens still. There's no experienced operator that leaves it as is
at this point, meaning the only people using 256 are the poor folks that
just got started using C*. I've worked with over a hundred clusters in the
l
Logistics aside, I think it is a good idea to default 1 token (or a low
number). Let the user understand what it means to go beyond 1 and tune things
based on their needs.
Dinesh
On Friday, September 21, 2018, 5:06:14 PM PDT, Jonathan Haddad
wrote:
One thing that's really, really bot
I agree that it should be lowered. What I’ve seen debated a bit in the past is
the number but I don’t think anyone thinks that it should remain 256.
> On Sep 21, 2018, at 7:05 PM, Jonathan Haddad wrote:
>
> One thing that's really, really bothered me for a while is how we default
> to 256 token
Also agree it should be lowered, but definitely not to 1, and probably
something closer to 32 than 4.
--
Jeff Jirsa
> On Sep 21, 2018, at 8:24 PM, Jeremy Hanna wrote:
>
> I agree that it should be lowered. What I’ve seen debated a bit in the past
> is the number but I don’t think anyone thi
+1 to lowering it.
Thanks Jon for starting this.We should create a JIRA to find what other
defaults we need revisit. (Please keep this discussion for "default token"
only. )
On Fri, Sep 21, 2018 at 8:26 PM Jeff Jirsa wrote:
> Also agree it should be lowered, but definitely not to 1, and probabl
> We should create a JIRA to find what other defaults we need revisit.
Changing a default is a pretty big deal, I think we should discuss any
changes to defaults here on the ML before moving it into JIRA. It's nice
to get a bit more discussion around the change than what happens in JIRA.
We (TLP
Putting it on JIRA is to make sure someone is assigned to it and it is tracked.
Changes should be discussed over ML like you are saying.
On Sep 21, 2018, at 21:02, Jonathan Haddad wrote:
>> We should create a JIRA to find what other defaults we need revisit.
>
> Changing a default is a pretty
Jon, thanks for starting this thread!
I have created CASSANDRA-14784 to track this.
Dinesh
> On Sep 21, 2018, at 9:18 PM, Sankalp Kohli wrote:
>
> Putting it on JIRA is to make sure someone is assigned to it and it is
> tracked. Changes should be discussed over ML like you are saying.
>
>
We are using 8 or 16 tokens internally, with the token allocation algorithm
enabled. The range distribution is good for us.
Dikang.
On Fri, Sep 21, 2018 at 9:30 PM Dinesh Joshi
wrote:
> Jon, thanks for starting this thread!
>
> I have created CASSANDRA-14784 to track this.
>
> Dinesh
>
> > On S
11 matches
Mail list logo
