Hi everyone,
I had a few people asking me recently about the Java 11 support.
I came across this thread we had last year -
https://lists.apache.org/thread.html/r38f6beaa22e247cb38212f476f5f79efdc6587f83af0397406c06d7c%40%3Cdev.cassandra.apache.org%3E
.
I think we have all tests running in both Java
One of the things I'm excited about with the 4+ releases is this running with
Java 17+ (including ZGC) so I would love to see this get more serious testing
and validation.
Anecdotal account - at an event a couple of years ago, I spoke to someone from
an education software company was running so
+1 for moving Java 11 support out of experimental for 4.0 at minimum, and no
concern with doing so for 3.0/3.11 if someone were to propose.
I and contributors I work with have deployed 4.0 + JDK11 in production, have
found no issues, and would treat any issues that arise as ones we’re able to
j
The design doc and CEP currently pass on blocklisting / denylisting writes
at this time. In the proposed new patch it states:
"Note: We do not want to blacklist writes since it is the reads that
primarily impact the performance when reading a bad partition, and we may
want writes to be allowed to “
+1 from me, any improvement in this area would be great.
It would be nice if this could include visibility into repair streams, but just
exposing the repair state will be a big improvement.
> On Aug 25, 2021, at 5:46 PM, David Capwell wrote:
>
> Now that 4.0 is out, I want to bring up improvin
>
> 2. Add retries to specific stages of coordination, such as prepare and
>validate. In order to do these retries we first need to know what the
state is for the participant which has yet to reply...
If I understand it correctly, does it mean retries only happen in the
coordinator and th
>
> I and contributors I work with have deployed 4.0 + JDK11 in production,
> have found no issues, and would treat any issues that arise as ones we’re
> able to jump on and contribute development + review resources to resolve in
> the project.
>
That's everything I need to hear. Let's remove the
The discussion came up on
https://issues.apache.org/jira/browse/CASSANDRA-16873 concerning where
we land different diff types and it was clear the conversation should
come to the ML and the outcome be codified for the future.
Some useful pre-reading on the Release Lifecycle on our wiki:
https://cw
+1 to both removal of experimental for 11, and moving trunk to 11+17
On Thu, Aug 26, 2021 at 12:35 PM Mick Semb Wever wrote:
>
> >
> > I and contributors I work with have deployed 4.0 + JDK11 in production,
> > have found no issues, and would treat any issues that arise as ones we’re
> > able to
+1 to both removal of experimental for 11, and moving trunk to 11+17
Em qui., 26 de ago. de 2021 às 14:40, Brandon Williams
escreveu:
> +1 to both removal of experimental for 11, and moving trunk to 11+17
>
> On Thu, Aug 26, 2021 at 12:35 PM Mick Semb Wever wrote:
> >
> > >
> > > I and contribu
Thank you, Josh for the elaborate explanation of a potential scenario where
denylisting writes would make sense.
I, 100% agree that could benefit in a situation where we would want to deny
writes to a partition that we do not have much control on (which is true in
most situations) and such behavior
Throwing my two cents out…
I'm keen for us to better adhere to SemVer rules (I've said this before).
Specifically defining the difference between a Major and a Minor version,
and defining the difference between a Minor and a Patch version (which in
turn addresses your questions Josh). But this i
+1 from me on both as well.
> On Aug 26, 2021, at 12:44 PM, Paulo Motta wrote:
>
> +1 to both removal of experimental for 11, and moving trunk to 11+17
>
>> Em qui., 26 de ago. de 2021 às 14:40, Brandon Williams
>> escreveu:
>>
>> +1 to both removal of experimental for 11, and moving trunk t
>
>
> Last but not least, do we know anyone running Java 11 in production?
> This thread was really opened as a stage to share our thoughts and
> hopefully come up with a plan as a community.
>
I am aware of many large deployments using Java11 and 4.0 in production. +1
on making this non experime
14 matches
Mail list logo
