have seen multiple times when authentication was failing under
> > the
> > > > > heavy
> > > > > >load because queries to system tables were timing out - with
> > these
> > > > > >defaults people may still have the possibility to get
ith
> these
> > > > >defaults people may still have the possibility to get updates to
> > > > >roles/credentials faster when specifying _update_interval_
> > variants
> > > of
> > > > >these configurations.
> > >
t; >these configurations.
> > > > 2. change default snitch from SimpleSnitch to
> > > GossipingPropertyFileSnitch -
> > > > we're anyway saying that SimpleSnitch is only appropriate for
> > > >single-datacenter deployments, and for r
tch to
> > GossipingPropertyFileSnitch -
> > >we're anyway saying that SimpleSnitch is only appropriate for
> > >single-datacenter deployments, and for real production we need to
> use
> > >GossipingPropertyFileSnitch - why not to set it as default?
> &
uction we need to use
> >GossipingPropertyFileSnitch - why not to set it as default?
> >
> >
> > Jeremy Hanna at "Wed, 22 Jan 2020 11:22:36 +1100" wrote:
> > JH> I mentioned this in the contributor meeting as a topic to bring up
> on
> >
yments, and for real production we need to use
>GossipingPropertyFileSnitch - why not to set it as default?
>
>
> Jeremy Hanna at "Wed, 22 Jan 2020 11:22:36 +1100" wrote:
> JH> I mentioned this in the contributor meeting as a topic to bring up on
> the list -
; I mentioned this in the contributor meeting as a topic to bring up on the
list - should we
JH> take the opportunity to update defaults for Cassandra 4.0?
JH> The rationale is two-fold:
JH> 1) There are best practices and tribal knowledge around certain properties
where people
JH> just know t
wrong).
> >
> > I'm sure there are others that would be safe to change. I'll review our
> > defaults we typically set and report back tomorrow.
> >
> > On Tue, Jan 21, 2020, 7:22 PM Jeremy Hanna
> > wrote:
> >
> > > I mentioned this in t
r meeting as a topic to bring up on the
> > list - should we take the opportunity to update defaults for Cassandra
> 4.0?
> >
> > The rationale is two-fold:
> > 1) There are best practices and tribal knowledge around certain
> properties
> > where people just know to
tunity to update defaults for Cassandra 4.0?
>
> The rationale is two-fold:
> 1) There are best practices and tribal knowledge around certain properties
> where people just know to update those properties immediately as a starting
> point. If it's pretty much a given that we set so
I mentioned this in the contributor meeting as a topic to bring up on the list
- should we take the opportunity to update defaults for Cassandra 4.0?
The rationale is two-fold:
1) There are best practices and tribal knowledge around certain properties
where people just know to update those
11 matches
Mail list logo
