I created CASSANDRA-1617
On Oct 12, 2010, at 1:51 PM, Michael Moores wrote:
> I have a cluster of 8 nodes with a replication factor of 3 and consistency of
> QUORUM.
> When I stop one node in the cluster I end up with socket read timeouts to
>
less affected.
--Michael
Hi,
I am running a 4 cluster cassandra with replication factor 3.
I have upgraded to 1.0.3 from 0.7.6
After a week of work I get this errors.
Does someone know what they mean?
Thanks
Michael
STG-Cass1 INFO [COMMIT-LOG-WRITER] 2011-12-12 22:51:19,943
CommitLogSegment.java (line 60) Creating new
Hi,
I am running a 4 cluster cassandra with replication factor 3.
I have upgraded to 1.0.3 from 0.7.6
After a week of work I get this errors.
Does someone know what they mean?
Thanks
Michael
STG-Cass1 INFO [COMMIT-LOG-WRITER] 2011-12-12 22:51:19,943
CommitLogSegment.java (line 60) Creating new
:462)
Thanks
Michael
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Tuesday, December 13, 2011 6:01 PM
To: dev@cassandra.apache.org
Subject: Re: 1.0.3 cassandra java.lang.AssertionError
It means a garbage collection took 0 ms, which is unexpected. It's
har
org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassan
draDaemon.java:337)
at
org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:107)
can someone tell me how to recover from that
thanks
Michael
It's weird,
The table was part of a KS "Index" which I deleted in the last week.
I do not know how did it come back.
I have deleted it again and run repair on all the nodes on the cluster and
now it seems ok.
Thanks
Michael
-Original Message-
From: aaron mo
cluster a few times but it did not help.
Thanks in advance for your help.
Michael
The kind of errors I get:
NYC-Cass3 ERROR [ScheduledTasks:1] 2012-01-03 05:54:16,392
AbstractCassandraDaemon.java (line 133) Fatal exception in thread Thread
NYC-Cass3 ERROR [ScheduledTasks:1] 2012-01-03 05
servers I sould be ok. but every time when 1 node is down I get
timeout when I try to read data
2012-01-09 11:58:33,325 WARN
[me.prettyprint.cassandra.connection.CassandraHostRetryService] -
What am I missing?
Thanks
Michael
Thank you for your reply
Do you know if there are documentation of hector I can read to understand this
behavior?
Thanks
Michael
-Original Message-
From: sc...@scode.org [mailto:sc...@scode.org] On Behalf Of Peter Schuller
Sent: Monday, January 09, 2012 5:29 PM
To: dev
nks for the ticket number and the patch - I'll see what I can do to
get those changes made in the DataStax init and pass it along upstream.
--
Kind regards,
Michael Shuler
Hi,
> I'd really, really like to see us ship a Prom compatible metrics endpoint
out of the box in C* that has low overhead. All the current OSS metrics
exporters that I've seen have massive overhead. I'm specifically looking
for sub-10s collection on clusters with a thousand nodes and 500+ table
://github.com/MichaelRoosz/php-cassandra
Best Regards,
Michael
+1
On 5/16/25 06:32, Brandon Williams wrote:
Proposing the test build of Cassandra 4.1.9 for release.
sha1: 82fc35b0136cc5f706032759d73ac5ae02c20871
Git: https://github.com/apache/cassandra/tree/4.1.9-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassand
> jdk. attach is needed for nodetool sjk hh. When someone tries to use
> that command, they get an error that JDK is expected. There isn't
> anything to do about that here.
Given we have functionality that depends on a JDK, and all our testing is done
with a JDK, I'm in favour of printing a w
After breaking the builds on 3.11 (a clumsy oversight, mea culpa, and a big
thanks to Paulo and Robert for fixing it so quickly), it's been kinda bugging
me that we don't send out build failure email notifications.
Jenkins does have this functionality: with "E-mail Notification" configuration
On 2020/07/15 21:58:52, Lorina Poland wrote:
> While creating a third-party page (CASSANDRA-15940), I decided to check the
> links in the Proven block on the home page
Closing the loop on this… completed and the website updated under
CASSANDRA-15964. Thanks Lorina!
> See that here:
> https://docs.google.com/document/d/1aeNtgyPAsKcNa0GSKvl2ywlFEj30714ry4Sb5turWeE/edit?usp=sharing
>
> This outline is not complete, just my initial scribblings. Certainly
> collaboration would be welcome.
This is awesome Lorina. It would also be great to see all non-versione
> I think the pragmatic thing to do is fix it now, and I'd strongly
> prefer to do that but wanted to check if there are any objections or
> things I hadn't considered?
+1
Thanks for giving this visibility and demonstrating we are serious about the
beta test cycle.
--
> > The vote will be open for 72 hours (longer if needed). Everyone who has
> > tested the build is invited to vote. Votes by PMC members are considered
> > binding. A vote passes if there are at least three binding +1s and no -1's.
> >
>
>
> This vote has passed, after 72 hours, with three b
On 2020/08/31 16:57:32, Mick Semb Wever wrote:
> >
> > The vote will be open for 72 hours (longer if needed). Everyone who has
> > tested the build is invited to vote. Votes by PMC members are considered
> > binding. A vote passes if there are at least three binding +1s and no -1's.
> >
>
>
On 2020/08/31 16:59:18, Mick Semb Wever wrote:
> >
> >
> > The vote will be open for 72 hours (longer if needed). Everyone who has
> > tested the build is invited to vote. Votes by PMC members are considered
> > binding. A vote passes if there are at least three binding +1s and no -1's.
> >
>
On 2020/08/31 17:07:19, Mick Semb Wever wrote:
> >
> >
> > The vote will be open for 72 hours (longer if needed). Everyone who has
> > tested the build is invited to vote. Votes by PMC members are considered
> > binding. A vote passes if there are at least three binding +1s and no -1's.
> >
>
On 2020/08/31 17:13:17, Mick Semb Wever wrote:
> >
> > This vote has passed, after 72 hours, with three binding +67s, and no
> > -1s.
> >
>
>
> *7* binding +1s
(ok, third time lucky…)
This vote has passed, after 72 hours, with eight binding +1s, and no -1s.
-
> Regarding CASSANDRA-12126 and 4.0 we are facing several options and
> Benedict, Sylvain and I wanted to get the community feedback on them.
>
> We can:
>
>1. Try to use Benedict proposal for 4.0 if the community has the
>appetite for it. The main issue there is some potential extra de
> Benedict suggested that Sylvain and I made the choice. Sylvain did not want
> to make the final call.
> I chose correctness. If it is a problem and people prefer to vote. It is
> perfectly fine for me too :-)
+1
Appreciate it having been raised for exposure and discussion Benjamin, and
happy
> Do we want them fixed before we release 4.0-RC or are they part of the
> testing of the RC release?
We are so unbearably close, it would be nice to see the beta tickets narrowed
(again) to just the most critical issues.
Tickets about creating new tests, and bugs edge-case, or not severe o
> I propose to:
>
>- update the documentation to clarify the meaning of the fix version as
>'The version in which the item must be fixed' (e.g 4.0-beta if the ticket
>must be fixed in a beta release)
>- create a 4.0-GA fix version and use it for the Quality testing tickets
>-
Done. Thanks!
On 2020/12/17 10:57:35, Benjamin Lerer wrote:
> Thanks Mick for raising that problem. Effectively, I got confused along the
> way.
>
> +1
>
> On Thu, Dec 17, 2020 at 11:56 AM Sam Tunnicliffe wrote:
>
> >
> >
> > > On 17 Dec
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1's.
The vote has passed with 3 binding and 3 non-binding +1s.
-
> Do you happen to know if there is any documentation impact to the change?
Not that I can see.
Neither of these page make reference about the minimal chronicle-queue versions
required
- https://cassandra.apache.org/doc/latest/new/auditlogging.html
- https://cassandra.apache.org/doc/latest/
> Should this page be removed from at least the Cassandra 4.0 documentation?
> Neither seems to have been updated beyond C* 3.0.
Good idea Lorina. Do please remove it.
We have now https://cassandra.apache.org/third-party/ anyway.
---
> I would like to request an exception to the Beta release to get the
> upgrade in place and to support arm64. Does anyone have any objection
> or concern to the upgrade? An entry in NEWS.txt will be added.
Thanks Jeff, Marcus, Brandon.
I will merge CASSANDRA-16384 and CASSANDRA-16392 today.
> An entry in NEWS.txt will be added.
I've skipped the NEWS.txt entry, as we don't do alpha|beta upgrade sections. I
should have checked that earlier.
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For addit
> I believe that there is an appetite for the bleeding edge snapshots where
> we do not guarantee stability and that the semver discussion is not
> finished yet but I would like us to let those discussions go for some
> follow up threads.
> My goal with this thread was to reach an agreement on a
> * We’re within line-of-sight to closing out beta scope. Any work people can
> do on remaining blockers will accelerate the project toward RC.
So, last call for last minute concerns, the plan is to cut 4.0-rc1 once
- those beta tickets are resolved,
- the gremlins around v5 native protocol
On 2024/09/04 14:04:08 Hardik Madhu wrote:
> Hi all,
>
> I'm very excited to see that GoCQL is now an official ASF project.
Hi Hardik!
You are more than welcome. Indeed cassandra-gocql-driver is still in a bit of
a bootstrapping process, and we definitely could use all kind of helping han
Hey, all,
I've been working on a greenfield Perl client for the CQL Binary
Protocol. Since this is a client-in-progress, and my question
is actually about the protocol, I guessed dev@ seemed like the better
list, but please let me know if I should relocate to client-dev@.
As always happens when
paul cannon writes:
> It has the same structure as a string map, but might not necessarily *be* a
> string map. I would guess that this phrasing is used because it may be
> possible to have multiple identical "keys" in this structure, which would
> not make sense in a [string map]. (Although I don
> Actually, I am not completely sure if Maven wrapper will play nicely
> with Ant stuff of yours as maybe it indeed looks for "mvn" on path and
> wrapper is invoked differently so it does not have to necessarily see
> it. I ll check it and let you know.
I misunderstood you Stefan.
If you woul
> The vote will be open for 72 hours (longer if needed). Everyone who
> has tested the build is invited to vote. Votes by PMC members are
> considered binding. A vote passes if there are at least three binding
> +1s and no -1's.
+1
-
> As a risk mitigator, I was hoping we could preserve
> the sub-URIs so the switch doesn't impact current users:
> - make sure /doc/3.11/ (and other supported versions) still works
> - rename /doc/latest/ to /doc/4.0/ but pointing to the existing version of
> the site just to be sure we have a wo
> is this version of the web page already "analytics friendly"? In the
> context of https://plausible.cassandra.apache.org/cassandra.apache.org
It is!
it is still getting hacked in, but it will soon be formally part of the design
and website generation.
> tl;dr Can we switch the website over to a temporary static-html
> version of the new design, while work on the final antora generated
> version continues?
done.
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.or
601 - 644 of 644 matches
Mail list logo
