cache.
It is quite handy for point releases when a rollback is required, and possible,
because of regressions.
Thanks.
J.
--
Julien Anguenot (@anguenot)
> On Feb 21, 2017, at 12:03 PM, Michael Shuler wrote:
>
> The Cassandra team is pleased to announce the release of Apache
>
Hey Mohammad,
Just send a message to user-unsubscr...@cassandra.apache.org
<mailto:user-unsubscr...@cassandra.apache.org> using the email address you
subscribed with and you should be good to go.
See header of page: http://mail-archives.apache.org/mod_mbox/cassandra-user/
J.
--
Hey Oskar,
I would comment and add all possible information to that Jira issue…
J.
--
Julien Anguenot (@anguenot)
> On Aug 2, 2016, at 8:36 AM, Oskar Kjellin wrote:
>
> Hi,
>
> Ran into the same issue when going to 3.5. Completely killed our cluster.
> Only way was t
Hey Jesse,
You might wanna check and comment against that issue:
https://issues.apache.org/jira/browse/CASSANDRA-11887
J.
--
Julien Anguenot (@anguenot)
> On Aug 2, 2016, at 3:16 AM, Jesse Hodges wrote:
>
> Hi, I've got a bit of a conundrum. Recently I upgraded from
w/ LZ4.
After disabling compression on commit logs the issue was gone on my side.
J.
--
Julien Anguenot (@anguenot)
> On Jul 22, 2016, at 2:10 PM, Juho Mäkinen wrote:
>
> After a few days I've also tried disabling Linux kernel huge pages
> defragement (echo never
Personally hoping both release models (tick tock and long term stable release)
will still co-exist after September.
J.
--
Julien Anguenot (@anguenot)
> On Jul 21, 2016, at 1:41 AM, Jonathan Haddad wrote:
>
> If I were starting a new project today, I'd go with 3.0. It
All good now. Thanks.
J.
--
Julien Anguenot (@anguenot)
> On Jul 8, 2016, at 4:10 AM, Jake Luciani wrote:
>
> Sorry, I totally missed that. Uploading now.
>
> On Thu, Jul 7, 2016 at 4:51 AM, horschi <mailto:hors...@gmail.com>> wrote:
> Same for 2.2.7.
>
Hey,
The Debian packages do not seem to have been published. Normal?
Thank you.
J.
> On Jul 6, 2016, at 4:20 PM, Jake Luciani wrote:
>
> The Cassandra team is pleased to announce the release of Apache Cassandra
> version 3.0.8.
>
> Apache Cassandra is a fully distributed database. It is
AM, Oskar Kjellin wrote:
> Hmm, no way we can do that in prod :/
>
> Sent from my iPhone
>
>> On 21 juni 2016, at 18:50, Julien Anguenot wrote:
>>
>> See my comments on the issue: I had to truncate and reinsert data in
>> these corrupted tables.
>>
&g
ues when querying using a driver? Because we get no
> results in the driver what so ever
>
> Sent from my iPhone
>
>> On 21 juni 2016, at 18:50, Julien Anguenot wrote:
>>
>> See my comments on the issue: I had to truncate and reinsert data in
>> these cor
bles tho.
>
> Did you resolve it?
>
> Sent from my iPhone
>
>> On 21 juni 2016, at 18:27, Julien Anguenot wrote:
>>
>> I have experienced similar duplicate primary keys behavior with couple
>> of tables after upgrading from 2.2.x to 3.0.x.
>>
>> See
3.5.0.jar:3.5.0]
>
> at
> org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:226)
> ~[apache-cassandra-3.5.0.jar:3.5.0]
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_72]
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_72]
>
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_72]
>
>
> Any help is much appreciated
--
Julien Anguenot (@anguenot)
Hey Otis,
hehe :-)
I do have the latest agents running but these metrics are still empty on my
side. Will take that issue on Sematext side then.
Thanks.
J.
> On Jun 15, 2016, at 8:26 AM, Otis Gospodnetić
> wrote:
>
> Hi,
>
> On Wed, Jun 15, 2016 at 8:58 A
ding writes and pending cluster ops) that never
got supported after Casandra 2.2.x. Did report the issue but it never got
fixed. Otis if you are listening? :-)
[…]
J.
--
Julien Anguenot (@anguenot)
referenced herein
> available at www.icapterms.com <http://www.icapterms.com/>. Please notify us
> by reply message if this link does not work.
>
--
Julien Anguenot (@anguenot)
ts “normally” when you do
>> disable auto-compaction? You actually see pending compactions on nodes
>> having high load correct?
>
> Nope.
>
>> All seems legit here. Using G1 GC?
> Yes
>
> Problems also occurred on nodes without pending compactions.
>
RUNNABLE 51.10% 1.29%
>486 SharedPool-Worker-34 RUNNABLE 51.06% 1.03%
> Note: Only top 10 threads (according cpu load) are shown!
>
>
>> On 12 Feb 2016, at 18:14, Julien Anguenot wrote:
>>
>> At the time when the load is high and
at moment.
> We have many tombstones, which does not removed.
> DroppableTombstoneRatio is 5-6 (greater than 1)
>
>> On 12 Feb 2016, at 15:53, Julien Anguenot wrote:
>>
>> Hey,
>>
>> What about compactions count when that is happening?
>>
>> J.
Hey,
What about compactions count when that is happening?
J.
> On Feb 12, 2016, at 3:06 AM, Skvazh Roman wrote:
>
> Hello!
> We have a cluster of 25 c3.4xlarge nodes (16 cores, 32 GiB) with attached 1.5
> TB 4000 PIOPS EBS drive.
> Sometimes one or two nodes user cpu spikes to 100%, load
onsibility and liability for the accuracy and content of this attachment
>> and for any damages or losses arising from any inaccuracies, errors,
>> viruses, e.g., worms, trojan horses, etc., or other items of a destructive
>> nature, which may be contained in this attachment and shall not be liable
>> for direct, indirect, consequential or special damages in connection with
>> this e-mail message or its attachment.
>
--
Julien Anguenot (@anguenot)
USA +1.832.408.0344
FR +33.7.86.85.70.44
Hey Jason,
Your RF=3, do you have 3 nodes up and running in this DC? We have seen
this issue with 2.1.x and cqlsh where schema changes would trigger the
"keyspace not found" error in cqlsh if not all nodes were up and
running when altering KS schema in a DC with NetworkTopologyStrategy
and RF=3. F
21 matches
Mail list logo
