Looks like complete and utter FUD.
In the latest attack, malicious emails containing links to sites hosting the
Java exploit are said to have been sent to armed forces of an unnamed NATO
country, and a US defense organization.
So this has nothing to do with J2SE or EE running containers.
If anyone finds that this effects servers / c*, please update us so we can
take mitigation measures.
Thanks.
On Wed, Jul 15, 2015 at 12:48 AM, Ariel Weisberg wrote:
> Hi,
>
> Sounds like this isn’t an issue with the runtime. It’s another
> plugin/webstart/whatever desktop issue that doesn’t eff
Looks like it dies with OOM:
https://gist.github.com/kluyg/03785041e16333015c2c
On Tue, Jul 14, 2015 at 12:01 PM, Mikhail Strebkov
wrote:
> OpsCenter 5.1.3 and datastax-agent-5.1.3-standalone.jar
>
> On Tue, Jul 14, 2015 at 12:00 PM, Sebastian Estevez <
> sebastian.este...@datastax.com> wrote:
>
Hi,
Sounds like this isn’t an issue with the runtime. It’s another
plugin/webstart/whatever desktop issue that doesn’t effect servers. I Googled
but didn’t find a precise description of what the issue is.
Regards,
Ariel
> On Jul 14, 2015, at 3:31 PM, Marcos Ortiz wrote:
>
> Regards to all Cas
Regards to all Cassandra´s users.
I just wanted to inform there is a new Java Zero Day exploit recently
discovered by Trend Micro around the Hacking Team massive leak.
This exploit is affecting the latest Java version 1.8.0.45, not Java 1.6
or 1.7, so, I´m just informing this to be aware of this
OpsCenter 5.1.3 and datastax-agent-5.1.3-standalone.jar
On Tue, Jul 14, 2015 at 12:00 PM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> What version of the agents and what version of OpsCenter are you running?
>
> I recently saw something like this and upgrading to matching version
What version of the agents and what version of OpsCenter are you running?
I recently saw something like this and upgrading to matching versions fixed
the issue.
On Jul 14, 2015 2:58 PM, "Mikhail Strebkov" wrote:
> Hi everyone,
>
> Recently I've noticed that most of the nodes have OpsCenter agent
Hi everyone,
Recently I've noticed that most of the nodes have OpsCenter agents running
at 300% CPU. Each node has 4 cores, so agents are using 75% of total
available CPU.
We're running 5 nodes with OpenSource Cassandra 2.1.8 in AWS using
Community AMI. OpsCenter version is 5.1.3. We're using Ora
* Graham Sanderson , 2015-07-13 18:21:08 Mon:
> > Is there a set of best practices for this kind of workload? We would
> > like to avoid interfering with reads as much as possible.
> Ironically in my experience the fastest ways to get data into C* are
> considered “anti-patterns” by most (but I hav
When you say schema to settle, do you means we provide proper consistency
level? I don't think there is a provision to do that in tool. Or I can
change the SYSTEM KEYSPACE definition of replication factor equal to number
of nodes?
I mean the nodes have to all be on the same schema version.
In the
Thank you Mikhail. I'll take a look at your utility.
On Jul 13, 2015 5:30 PM, "Mikhail Strebkov" wrote:
> Hi Saladi,
>
> Recently I faced a similar problem, I had a lot of CFs to fix, so I wrote
> this: https://github.com/kluyg/cassandra-schema-fix
> I think it can be useful to you.
>
> Kind rega
11 matches
Mail list logo
