fig.
>
> That said with logback currently at 1.2.3 (in trunk), perhaps we
> should consider an upgrade for safety.
>
>> On Tue, Dec 14, 2021 at 8:50 AM Steinmaurer, Thomas
>> wrote:
>>
>> Any thoughts what the logback folks have been filed here?
>> http
Any thoughts what the logback folks have been filed here?
https://jira.qos.ch/browse/LOGBACK-1591
Thanks!
-Original Message-
From: Brandon Williams
Sent: Sonntag, 12. Dezember 2021 18:56
To: dev@cassandra.apache.org
Subject: Recent log4j vulnerability
I replied to a user- post about thi
Good to hear that discussion moves forward in this regard! Java11 got quite
some improvements in G1, especially for mixed collections.
Are there any plans to allow 3.11 running with Java 11 as well? We are
currently on Cassandra 3.11 and it’s the only Java process in our deployment
stack which
Java 11 support in Cassandra 3.11 would be fantastic. Is this something the
Cassandra project will follow-up or is this a dead-end in favor of Cassandra
4.0, although Java 11 is marked as "experimental" there. Not sure what this
means for production usage. 😊
Thanks,
Thomas
-Original Messa
I think there is also an issue with 3.0.19+ which prevents starting up
Cassandra on Windows at all, thus ideally some sort of fix in that area would
be nice to be included as well.
Regards,
Thomas
-Original Message-
From: Mick Semb Wever
Sent: Dienstag, 28. Jänner 2020 07:40
To: dev@ca
Hello,
as we are periodically hit in production by the following memory leak with
3.0.18: https://issues.apache.org/jira/browse/CASSANDRA-15400
Is there any ETA for 3.0.20?
Thanks,
Thomas
The contents of this e-mail are intended for the named addressee only. It
contains information that may be
Hello,
am I right that Java 11 support will only be in Cassandra 4.0 and not in future
releases of the 3.11.x series? Just want to be sure.
Thanks,
Thomas
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the
Hello,
on Windows 10, Cassandra 4.0 (trunk Nov 12) is crashing upon startup with Java
11, SIGAR related. Startup with Java8 works fine. Is this a known issue?
First part of the hs_err_pid file.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION
> In trunk you need to provide JAVA_HOME to both java8 and java11, like this
> for example;
>
> $ JAVA8_HOME= JAVA_HOME= ant artifacts
>
> /Marcus
>
> On Mon, Nov 12, 2018 at 09:21:10AM +, Steinmaurer, Thomas wrote:
> > Hello,
> >
> > I'm trying to st
Hello,
I'm trying to start with some first C* 4.0 experiments, thus tried to locally
build and create binary tarball artifcats. While this has worked e.g. with
3.11, I can't create a binary tarball for 4.0 anymore.
What I did locally:
* Switched from branch cassandra-3.11 to trunk
* ant realcle
Hello,
checked out Cassandra 3.11.3 to debug something.
Eclipse 4.8.0 Photon (Build id: 20180619-1200) complains on the following
compile error:
The method map(Function) in the type Stream is
not applicable for the arguments (((transform != null) ? transform : (
cell) -> "")) Abs
IMHO, stability and manageability (want to have the old (2.1) full repair
behavior back 😊, yes I followed the repair scheduling thread here) should be
the top priority before adding any new CQL enhancements or whatever.
Manageability improvements even treated for backports into 3.11.x, as it see
Having https://issues.apache.org/jira/browse/CASSANDRA-12269 in mind, 3.0 was a
noticeable step back regarding write throughput compared to what we have been
used with 2.1 on the same infrastructure, thus for us, 3.0.x is a no-go, thus
planning more towards the 3.11.x series in pre-production st
Hi,
if you are talking about on-heap troubles, then the following might be related
in 3.11.x:
https://issues.apache.org/jira/browse/CASSANDRA-13929
Thomas
-Original Message-
From: Micha [mailto:mich...@fantasymail.de]
Sent: Dienstag, 12. Dezember 2017 09:24
To: dev@cassandra.apache.org
s
linked https://issues.apache.org/jira/browse/CASSANDRA-10990
So it should be fine in all latest 3.x versions.
-Jeremiah
> On Oct 13, 2017, at 3:34 AM, Steinmaurer, Thomas
> wrote:
>
> Same here, regarding sincere question to know the corner cases from 2.1 =>
> 3.11.1, but Marcus
Same here, regarding sincere question to know the corner cases from 2.1 =>
3.11.1, but Marcus already provided the JIRA ticket.
Thanks!
-Original Message-
From: Per Otterström [mailto:per.otterst...@ericsson.com]
Sent: Freitag, 13. Oktober 2017 09:01
To: dev@cassandra.apache.org
Subject
Hi Jeff,
I was under the impression that streaming in a cluster with mixed binary
versions might be problematic, but as long as the cluster is on the same binary
version (e.g. after a rolling upgrade), we still can have SStables in mixed
data formats and streaming will work?
Thanks,
Thomas
--
. Oktober 2017 23:09
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Release Apache Cassandra 3.11.1
Same boat as Jeff, +1 since it’s not a regression.
> On Oct 2, 2017, at 2:04 PM, Steinmaurer, Thomas
> wrote:
>
> Jeff of course, not Jon. Sorry :-)
>
>
> -Origina
Jeff of course, not Jon. Sorry :-)
-Original Message-
From: Steinmaurer, Thomas [mailto:thomas.steinmau...@dynatrace.com]
Sent: Montag, 02. Oktober 2017 22:58
To: dev@cassandra.apache.org
Subject: RE: [VOTE] Release Apache Cassandra 3.11.1
Jon,
yes I also did see it with 3.11.0
Mon, Oct 2, 2017 at 1:29 PM, Steinmaurer, Thomas <
thomas.steinmau...@dynatrace.com> wrote:
> Jon,
>
> please see my latest comment + attached screen from our monitoring here:
> https://issues.apache.org/jira/browse/CASSANDRA-13754?
> focusedC
rguable worse to hold them back :\
>
> —
> AY
>
> On 2 October 2017 at 20:54:38, Steinmaurer, Thomas
> (thomas.steinmau...@dynatrace.com) wrote:
>
> Jeff,
>
> even if it is not a strict regression, this currently forces us to do a
> rolling restart every ~ 72hrs to be
Jeff,
even if it is not a strict regression, this currently forces us to do a rolling
restart every ~ 72hrs to be on the safe-side with -Xmx8G. Luckily this is just
a loadtest environment. We don't have 3.11 in production yet.
I can offer to immediately deploy a snapshot build into our loadtest
Hello,
posted also to the users list, but possibly it is better targeted to this list,
cause 3.11.1 is close to be released?
We were facing a memory leak with 3.11.0
(https://issues.apache.org/jira/browse/CASSANDRA-13754) thus upgraded our
loadtest environment to a snapshot build of 3.11.1. Ha
23 matches
Mail list logo
