presentative of the committee. A
> list of Apache Cassandra PMC members can be found on:
> https://cassandra.apache.org/_/community.html
>
> Kind regards,
>
> Paulo
>
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
s.
> > > >
> > > > [1]: CHANGES.txt:
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0.0-tentative
> > > > [2]: NEWS.txt:
> > > >
> > >
section.
> > Given that criteria, Professional Support and Education might be on the
> > chopping
> > block as well.
> >
>
> +1 would definitely make my life easier when I'm reviewing/pushing updates
> to the site. 🍻
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
On Thu, Jun 24, 2021 at 2:38 AM Joshua McKenzie
wrote:
>
> The obvious core responsibility of the website should be to ASLv2
> permissively licensed Apache Cassandra and secondarily to CQL as a protocol
> IMO. I don't think we as a project should be tracking derivative works,
> forks, or other th
> > > >>>>
> > > >>>>
> > > >>
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-rc2-tentative
> > > >>>> [3]: The maven artifacts were accidentally prematurely made
> public.
> > Docs
> > > >>>> have been updated to prevent this happening again.
> > > >>>>
> > > >>
> > > >>
> > > >>
> -
> > > >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > >> For additional commands, e-mail: dev-h...@cassandra.apache.org
> > > >>
> > > >>
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
---
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
org/ecosystem/
> > .
> >
> > If you have edits or know of other third-party Cassandra projects, tools,
> > products, etc that may be useful to others -- please get in touch and
> we'll
> > add to the next round of site updates in July.
> >
> > Thanks!
> >
> > Melissa
> > Apache Cassandra Contributor
> >
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
gt;>>>> On Fri, May 14, 2021, 8:03 AM Mick Semb Wever
> > >>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>> The PMC members are pleased to announce that Caleb Rackliffe
> has
> > >>>>>>>>> accepted the invitation to become
additional commands, e-mail: dev-h...@cassandra.apache.org
> >>>>
> >>>>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
> --
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
ache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
>
> -----
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
>
>
>
> The LICENSE and NOTICE issues remain unassigned, if you are keen!
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
sible.) And we are not looking at impacting QA or touching any
> compatibility aspect of the code.
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
.
> >
> >
> > [1]: CHANGES.txt:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-rc1-tentative
> > [2]: NEWS.txt:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=re
>>> Y(n-2): Supported for high severity correctness/bugs for 1 more
> year
> > (1
> > > >> bugfix)
> > > >>
> > > >> This sounds excellent to me, +1.
> > > >>
> > > >>
> -
> > > >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > >> For additional commands, e-mail: dev-h...@cassandra.apache.org
> > > >>
> > > >>
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >
> > >
> >
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
resources -- or community photos --
> > please reply to me and we'll add.
> >
> > Site for review: https://cassandra.staged.apache.org/
> >
> > https://issues.apache.org/jira/browse/CASSANDRA-16115
> >
> > Melissa Logan
> >
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
t; -
> >
> > Cluster-level Stop / Resume - stop all running instances while keeping
> > persistent storage. Allows for scaling compute down to zero. Bringing the
> > cluster back up follows expected startup procedures
> >
> > Road Map / Inflight
> >
> >
tion the project then
> > > collaborates on. There's no mass adoption evidence nor feature
> enumeration
> > > that I know of for any of the approaches anyone's taken, so the
> > > discussions
> > > remain stalled.
> > >
> > > On Wed
nd seeing which
> ones meet the needs of end users before talking about adopting one into the
> foundation.
>
> Great to hear that you folks are joining forces though! Bodes well for C*
> users that are wanting to run things on k8s.
>
>
>
> On Tue, Sep 22, 2020 at 4:
s. We need to document what functionality an operator should
> include at level 0, level 1, etc. We did discuss this a good bit during
> some of the initial SIG meetings, but I guess it wasn't really a focal
> point at the time. I think we should also provide references to existing
>
the approach and I'm looking
forward to folks other suggestions!
Cheers
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | (650) 284 9692
016/01/new-token-allocation-algorithm-cassandra-30
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | (650) 284 9692
+1
On Mon, Nov 4, 2019 at 10:56 AM Vinay Chella
wrote:
> +1
>
> -Vinay Chella
>
> On Sat, Nov 2, 2019 at 5:09 PM Jeff Carpenter
> wrote:
>
> > FYI the audio of the session with Ben Bromhead / Scott Andreas is
> > available:
> >
> >
> https://fe
On Wed, Sep 18, 2019 at 6:43 AM Cyril Scetbon
> >> wrote:
> >>>>
> >>>> Hey guys,
> >>>>
> >>>> I heard that at the last summit there were discussions about providing
> >> an
> >>>> official docker image to run Cassandra on Kubernetes. Is it something
> >> that
> >>>> you’ve started to work on ? We have our own at
> >>>> https://github.com/Orange-OpenSource/cassandra-image <
> >>>> https://github.com/Orange-OpenSource/cassandra-image> but I think
> >>>> providing an official image makes sense. As long as we can easily do
> >>>> everything we do today. We could also collaborate.
> >>>>
> >>>> Thank you
> >>>> —
> >>>> Cyril Scetbon
> >>>>
> >>>>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | (650) 284 9692
o cwiki.
> >
> > If you only need couple pages, feel free to move the content to the
> > documentation. I'm sure we can also export the wiki in its entirety and
> > put it somewhere offline, if there's a concern about maybe needing some
> of
> > the
be on vacation.
> > Everyone is welcome to ignore the result until I get back in a couple of
> > weeks, or if anybody is eager feel free to close the vote and take some
> > steps towards implementation.
> > >
> >
> >
> > --
e are already paying. I
> am not saying they are directly related.
>
> I'll wait a week for discussion and if there is consensus make the change.
>
> Regards,
> Ariel
>
> -----
> To unsubscribe, e-mail: d
t; > > >>>>>>
> > > >>>>
> > > >>>
> > > >>
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__incubator.apache.org_guides_ip-5Fclearance.html&d=DwIFAg&c=adz96Xi0w1RHqtPMowiL2g&r=CNZK3RiJDLqhsZDG6FQGnXn8WyPRCQhp4x_uBICNC0g&m=g-MlYFZVJ7j5Dj_ZfPfa0Ik8Nxco7QsJhTG1TnJH7xI&s=rk5T_t1HZY6PAhN5XgflBhfEtNrcZkVTIvQxixDlw9o&e=
> > > >>>>>>
> > > >>>>>> Pending the outcome of this vote, we will create the JIRA issues
> > for
> > > >>>>>> tracking and after we go through the process, and discuss adding
> > > >>>>>> committers in a separate thread (we need to do this atomically
> > > >> anyway
> > > >>>>>> per general ASF committer adding processes).
> > > >>>>>>
> > > >>>>>> Thanks,
> > > >>>>>> -Nate
> > > >>>>>>
> > > >>>>>>
> > > >>
> -
> > > >>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > >>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > -
> > > >>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > >>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > -
> > > >>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > >>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> > > >>>>
> > > >>>>
> > > >>>
> > > >>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >
> > >
> >
>
>
> --
> Jon Haddad
> http://www.rustyrazorblade.com
> twitter: rustyrazorblade
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Reliability at Scale
Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer
nything this year?
> > We
> > > > may
> > > > > also be able to provide space in bay area and help to organize it.
> > > > (Please
> > > > > let us know, so we could get final approval for that).
> > > > >
> > > >
wn already.
> >
> > Nate, now that I've spoken for you, you can clarify, :D
> >
> > Patrick
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
> --
t;
>
> On Mon, Jul 23, 2018 at 2:25 PM Ben Bromhead wrote:
>
> > The year has gotten away from us a little bit, but now is as good a time
> as
> > any to put out a general call for interest in an NGCC this year.
> >
> > Last year Gary and Eric did an awesome job
other sponsors (doesn't have to be monetary, can be space,
resource etc) who want to get involved?
If folks are generally happy with the end approach we'll post details as
soon as possible (given its July right now)!
Ben
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com
t; >>
> > >> Vote will be open for 72 hours.
> > >>
> > >> Thanks,
> > >> Sankalp
> > >>
> > >> [1]
> > >>
> > >> https://lists.apache.org/thread.html/494c3ced9e83ceeb53fa127e44eec6
> > e2588a01b769896b25867fd59f@%3Cdev.cassandra.apache.org%3E
> > >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Reliability at Scale
Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer
sible, moving us towards an eventual goal of not needing to
> feature-freeze at all.
>
> regards,
> Mick
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apach
s
> >>>> that each port number appears to be a discrete instance of the
> server. So
> >>>> you could have shards be actual shards that are simply colocated on
> the
> >>>> same box, run in the same process, and share resources. I know this
>
have those
> > packets delivered directly to the core that will service them.
> >
> >
> > (also, some protocol changes are needed so the driver knows how tokens
> > are distributed among shards)
> >
> > On 2018-04-19 19:46, Ben Bromhead wrote:
> &
implementations regardless of how they may look like.
> >
> > >
> > > Do we have driver authors who wish to support both projects?
> > >
> > > Surely, but I imagine it would be a minority. ​
> > >
> >
> > -
we can start talking to/planning around.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
> --
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650
I would also suggest if you can't commit to June 2 due to timing or feature
set. If you could provide the absolute minimum date / features that would
let you commit to testing, that would be useful.
On Thu, Apr 12, 2018 at 3:49 PM Ben Bromhead wrote:
> We (Instaclustr) are also happ
ess any
> >> > easier.
> >>
> >>
> >> It changes the interest level of at least some of the people able to
> >> properly test it from "not willing" to "willing".
> >>
> >> Totally possible that there exist people who a
can do whatever we
> want in
> > > terms of dropping a new feature 4.1/5.0 (or whatev.) whenever we
> want.
> > >
> > > In thinking about this, what is stopping us from branching 4.0 a
> lot
> > > sooner? Like now-ish? This will let f
ternative would help.
Otherwise if no one chimes in I would propose sticking with June 1.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.ap
sting and dogfooding
> > implied by such before a GA)
> >
> > How do folks feel about the above points?
>
> +1
> +1
>
> :)
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cass
ere that's going to win
> over
> >> users. It's mostly refactorings and improvements that affect developers
> >> more so than users. I'm really interested in why people believe there
> is an
> >> actual benefit in pumping out feature releases on a yearly basis. Who
> >> exactly does
anding that it might not fully work out of the box the first
> >>>>>>> time we ship it. We have to be willing to take risks but we also
> >>> have
> >>>>>>> to be honest with our users. It may help build confidence if a few
> >>>>>>> major deployments use it (such as Netflix) and we are happy of
> >>> course
> >>>>>>> to provide that QA as best we can.
> >>>>>>>
> >>>>>>> -Joey
> >>>>>>>
> >>>>>>> On Tue, Apr 3, 2018 at 10:48 AM, Blake Eggleston
> >>>>>>> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Hi dev@,
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> The question of the best way to schedule repairs came up on
> >>>>>>>> CASSANDRA-14346, and I thought it would be good to bring up the
> >>> idea
> >>>>>>>> of an external tool on the dev list.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Cassandra lacks any sort of tools for automating routine tasks
> >>> that
> >>>>>>>> are required for running clusters, specifically repair. Regular
> >>>>>>>> repair is a must for most clusters, like compaction. This means
> >>>> that,
> >>>>>>>> especially as far as eventual consistency is concerned, Cassandra
> >>>>>>>> isn’t totally functional out of the box. Operators either need to
> >>>>>>>> find a 3rd party solution or implement one themselves. Adding this
> >>>> to
> >>>>>>>> Cassandra would make it easier to use.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Is this something we should be doing? If so, what should it look
> >>>> like?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Personally, I feel like this is a pretty big gap in the project
> >>> and
> >>>>>>>> would like to see an out of process tool offered. Ideally,
> >>> Cassandra
> >>>>>>>> would just take care of itself, but writing a distributed repair
> >>>>>>>> scheduler that you trust to run in production is a lot harder than
> >>>>>>>> writing a single process management application that can failover.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Any thoughts on this?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Blake
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>> -
> >>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>> -
> >>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Thank you & Best Regards,
> >>> --Simon (Qingcun) Zhou
> >>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
> --
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Reliability at Scale
Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer
t; - Stefan's Vault integration work. A sub-ticket, CASSANDRA-14102,
> > > addresses
> > > > encryption at-rest, subsumes CASSANDRA-9633 (SSTable encryption) -
> > which
> > > I
> > > > doubt I would be able to get to any time this year. It would
>
tions. Add
> your suggestions for new major features you desire to be added for version
> 4.0 only. Keep it simple, not detailed yet. That comes a few steps from
> now. What we have is a basic collaboration challenge. No problem.
>
> Kenneth Brotman
>
>
>
>
>
> --
Ben
here are my lists to get us started.
>> 1.
>> CASSANDRA-8460 - Tiered/Cold storage for TWCS
>> <https://issues.apache.org/jira/browse/CASSANDRA-8460>
>> CASSANDRA-12783 - Batchlog redesign
>> <https://issues.apache.org/jira/browse/CASSANDRA-12783>
>> CASSA
have been fixed in 3.11.1 and 3.0.15, the remaining
> > bugs mostly only affect views with a poor data model. Plus we've already
> > required the known broken components require a flag to be turned on.
>
> -
> To unsubscribe, e-mail: dev-unsubscr
; giant warning statement about how it is an experimental feature I
> > >> think
> > >>>>> that is pretty visible during development?
> > >>>>>
> > >>>>> I guess I can see just blocking new ones without a flag set, but we
> > >> need
> > >>>>>
ne it would just prevent users from
> creating new MVs, and maybe log warnings on startup for existing MVs if the
> flag isn’t enabled.
> >
> > Let me know what you think.
> >
> > Thanks,
> >
> > Blake
>
>
> ----
; Josh - want to make sure folks are not duplicating effort here, is the
> > status of the above on your radar? Regardless, I appreciate the
> > communication. Thanks for that!
> >
> > -----
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.ap
+1
On Fri, 2 Jun 2017 at 13:17 Eric Evans wrote:
> On Fri, Jun 2, 2017 at 2:34 PM, Ben Bromhead wrote:
> > We are more than happy to donate some resources (both people and
> materials)
> > to putting on NGCC.
> >
> > I would suggest some sort of committee of f
; > --
> > Eric Evans
> > john.eric.ev...@gmail.com
> >
> > ---------
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
rrently storage engine is a log structured merge tree. RocksDB
does it's own thing.
Again this is an implementation detail about where the storage engine
interface line is drawn, but from the above example compaction I think it
is a non issue?
> And not even mentioning the other operation
;
> https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
> get this done with INFRA.
>
> Vote will be open for 72 hours.
>
> Thanks,
>
> -Jason Brown
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
winski
> > > Ariel Weisberg
> > > Blake Eggleston
> > > Alex Petrov
> > > Joel Knighton
> > >
> > > Congratulations all! Please keep the excellent contributions coming.
> > >
> > > Thanks,
> > >
> > > -Jason Brown
> > >
> >
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
;
> -Jason
>
> On Tue, Feb 7, 2017 at 7:26 PM, Ben Bromhead wrote:
>
> > As part of our commitment to contributing back to the Apache Cassandra
> open
> > source project and the wider community we are always looking for ways we
> > can foster knowledge sharing an
welcoming of foreign students.
We are also open to sponsoring a PhD project with a more in depth focus for
the right candidate.
For more details please don't hesitate to get in touch with myself or reach
out to i...@instaclustr.com.
Cheers
Ben
--
Ben Bromhead
CTO | Instaclustr &
(current and previous) to do bug fix support at any
> > given time.
>
> The third reason is particularly appealing.
>
> +1 on six months.
> +1 on killing tick/tock at 3.10 (with a potential bugfix follow up per
> the other thread).
>
--
Ben Bromhead
CTO | Instaclu
(kohlisank...@gmail.com)
> wrote:
>
> The point Ben is saying is that for auth keyspace, default o​f RF=1 is not
> good for any type of cluster whether it is small or large.
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
o easy for us to maintain separately, I'm just trying to figure
out where I'm missing the point and if we need to re-evaluate the way we do
things or if the fear of misuse is the primary concern :)
On Wed, 30 Nov 2016 at 10:32 Jeff Jirsa wrote:
>
>
> On 2016-11-30 10:02 (-0800),
e 2016 15:30
> > >> To: dev@cassandra.apache.org
> > >> Subject: Where do I find EverywhereStrategy?
> > >>
> > >> I came across the class name
> > >> "org.apache.cassandra.locator.EverywhereStrategy" in an error message,
> > so I
> > >> started searching through the code for it. I can't seem to find it.
> Any
> > >> pointers?
> > >>
> > >>
> > >> Thanks,
> > >>
> > >>
> > >> James
> > >>
> >
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
p in Cupertino. I'm nervous about that. Not
> that that ya'll are not capable, I'm solely looking at it from the
> "that is a big list of some pretty hard shit" perspective.
>
> So what else do we need to discuss to get these completed? How and
> where can other folks pitch in?
>
> -Nate
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
s/materialised views/aggregates/
also we expect to have our first larger production 3.7 LTS cluster in the
next few months.
On Thu, 17 Nov 2016 at 15:38 Ben Bromhead wrote:
> We have a few small customers clusters running on our 3.7 LTS release...
> though we are not calling it prod
uot;new stuff that could/will
> break
> > > >> things"
> > > >> > > > > given we are upping
> > > >> > > > > the major version.
> > > >> > > > >
> > > >> > > >
> > >
cassandra.apache.org%3E
> [4]
>
> https://lists.apache.org/list.html?priv...@cassandra.apache.org:lte=1M:Apache%20trademark%20and%20Spring%20project%20names
> [5] https://mesosphere.github.io/cassandra-mesos/
> [6] https://github.com/riptano/cassandra-dtest
> [7]
>
> https://lists.apache.org/thread.html/d43300016d3871587c43eea8cd4223221904fddc7916d9d6d858bd29@%3Cprivate.cassandra.apache.org%3E
> [8]
>
> https://lists.apache.org/thread.html/d9e694ba8eaac8e8c70cbfd3f6ee249d43f8c67279882ffc65e56cac@%3Cdev.cassandra.apache.org%3E
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
is more active.
> >
> > This vote will remain open for 72 hours.
> >
> > 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org
> >
> >
> >
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
Include table name in "Cannot get comparator"
> exception(CASSANDRA-12181)
> 27. Collect metrics on queries by consistency level (CASSANDRA-7384)
> 28. processs restarts are failing becase native port and jmx ports are in
> use(CASSANDRA-11093)
>
> Thanks,
> Sankalp
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
gt; >>> I have cherry picked & merged the patch back to here and will put it
> in a
> >>> JIRA as well tonight, I just wanted to get the ball rolling asap on
> this.
> >>>
> >>>
> >>
> https://github.com/rustyrazorblade/cassandra/tree/fix_commitlog_exception
> >>>
> >>> Jon
> >>>
> >>
> >>
>
> --
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
;gt; &gt;
> >> &gt; -Jeremiah
> >> &gt;
> >> &gt; &gt; On Oct 7, 2016, at 1:02 PM,
Prasenjit Sarkar &
> >> lt;prasenjit.sar...@datos.io&gt;
> >> &gt; wrote:
> >> &gt; &gt;
> >> &gt; &gt; Hi everyone,
> >> &gt; &gt;
> >> &gt; &gt; To the best of my
understanding that Datastax has proprietary
> >> replication
> >> &gt; &gt; strategies: Local and
Everywhere which are not part of the open
> >> source
> >> &gt; &gt; Apache Cassandra project.
> >> &gt; &gt;
> >> &gt; &gt; Do we know of any plans in
the open source Cassandra driver
> >> community to
> >> &gt; &gt; support these two
replication strategies? Would Datastax have a
> >> licensing
> >> &gt; &gt; concern if the open source
driver community supported these
> >> strategies?
> >> &gt; I'm
> >> &gt; &gt; fairly new here and would
like to understand the dynamics.
> >> &gt; &gt;
> >> &gt; &gt; Thanks,
> >> &gt; &gt; Prasenjit
> >> &gt;
> >> &gt;
> >>
> >>
> >>
> >>
> >>
> >>
>
>
>
>
>
--
Ben Bromhead
CTO | Instaclustr <https://www.instaclustr.com/>
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer
some tickets around this as well as our
in-progress multi-tennant solution just uses containers, namespaces et al for
isolation.
Cheers
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359
On 31/08/2014, at 10:06 AM, Jay Patel wrote:
> Hi Folks,
>
> Ideall
No worries, message sent
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359
On 18 Dec 2013, at 10:35 am, Aleksey Yeschenko wrote:
> Hi Ben,
>
> Send it to me, I'll handle it.
>
> Thanks
>
>
> On Wed, Dec 18, 2013 at 2:30 AM, Ben B
Cassandra project should have
secur...@cassandra.apache.org mailing address, where sensitive issues can be
reported to the core dev team without it being made public.
Regards
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359
your limits.conf.
Under other OS's that use RBAC style permissions, for example Solaris, where
capabilities are often specified according to project, role, service etc the
capability may need to be explicitly set.
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
On 22/08/201
74 matches
Mail list logo
