Re: Cassandra Stress Tool - Insert data in a pace

On 08/04/2017 01:16 PM, Lucas Benevides wrote: > I want to test, in a lab, the behavior of the compaction strategies. I > found Cassandra Stress Tool very useful, but it does not have an option to > insert data in a chosen pace, i. e. insert data along a period, with just a > certain amount of data

Re: State of Materialized Views

I asked the same question on IRC a couple days ago and Aleksey asked if I could hold for CASSANDRA-13595. -- Kind regards, Michael On 09/22/2017 01:02 PM, Ben Bromhead wrote: > Just saw that https://issues.apache.org/jira/browse/CASSANDRA-11500 got > commited 4 days ago, awesome stuff and a huge

Re: Expected release date for 3.11.1?

On 09/27/2017 02:40 PM, Vincent Lee wrote: > Anyone has an approximate date when 3.11.1 will be released? > Interested to get fix for CASSANDRA-13752 The issues currently in progress for 3.11.1 are: CASSANDRA-13595 Implement short read protection on partition boundaries CASSANDRA-13808 Integer ov

Re: Expected release date for 3.11.1?

; tickets. If we can wait that long, great. If we feel an urge to go ahead now, > then it’ll have to be 3.0.16/3.11.2 for fully working short read protection. > > — > AY > > On 28 September 2017 at 00:04:13, Michael Shuler (mich...@pbandjelly.org) > wrote: > > On 09/2

[VOTE] Release Apache Cassandra 2.1.19

I propose the following artifacts for release as 2.1.19. sha1: 428eaa3e37cab7227c81fdf124d29dfc1db4257c Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.19-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1148/org/apac

[VOTE] Release Apache Cassandra 2.2.11

I propose the following artifacts for release as 2.2.11. sha1: c510e001481637e1f74d9ad176f8dc3ab7ebd1e3 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.11-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1149/org/apac

[VOTE] Release Apache Cassandra 3.0.15

I propose the following artifacts for release as 3.0.15. sha1: b32a9e6452c78e6ad08e371314bf1ab7492d0773 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.15-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1150/org/apac

[VOTE] Release Apache Cassandra 3.11.1

I propose the following artifacts for release as 3.11.1. sha1: 983c72a84ab6628e09a78ead9e20a0c323a005af Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1151/org/apac

Re: [VOTE PASSED] Release Apache Cassandra 2.1.19

With 10 binding +1, 1 non-binding +1, and no other votes, this vote passes. I'll get the artifacts published today. -- Kind regards, Michael On 09/28/2017 01:11 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.19. &

Re: [VOTE PASSED] Release Apache Cassandra 2.2.11

With 10 binding +1, 3 non-binding +1, and no other votes, this vote passes. I'll get the artifacts published today. -- Kind regards, Michael On 09/28/2017 01:40 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.11. &

[RELEASE] Apache Cassandra 2.1.19 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.1.19. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source a

[RELEASE] Apache Cassandra 2.2.11 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.2.11. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source a

Re: [VOTE PASSED] Release Apache Cassandra 3.0.15

With 8 binding +1, 1 non-binding +1, and no other votes, the 3.0.15 vote has passed. I'll get the artifacts published soon. -- Kind regards, Michael On 10/02/2017 12:18 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.15. &

Re: [VOTE] Release Apache Cassandra 3.11.1

I count 7 binding +1 votes and no other votes for the 3.11.1 release. Thanks for all the feedback. I will publish the release artifacts shortly. -- Kind regards, Michael On 10/02/2017 12:58 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.1. >

Re: [VOTE PASSED] Release Apache Cassandra 3.11.1

On 10/09/2017 10:15 AM, Michael Shuler wrote: > I count 7 binding +1 votes and no other votes for the 3.11.1 release. > Thanks for all the feedback. I will publish the release artifacts shortly. > Resend with subject updated to [VOTE PASSED] :) --

CassCI will be shut down 10/31

Hi all, cassci.datastax.com will be shut down at the end of October. Joaquin sent me a dtest docker work in progress patch to look at and unfortunately, I have not had the free time to dig into it, but it looks like a good idea. It could be docker, kubernetes, or something else to parallelize dtes

[RELEASE] Apache Cassandra 3.11.1 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.11.1. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source a

[RELEASE] Apache Cassandra 3.0.15 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.0.15. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source a

Re: Cassandra DTests deadlocks on random test

7.6G RAM may be a little bit too small, we've seen similar random hangs in the past on non-resource-intensive tests on m3.large. It doesn't appear you are skipping resource-intensive tests. Our standard dtest instance type has been an m3.xlarge, and the resource-intensive tests are run m3.2xlarge.

Re: Cassandra DTests deadlocks on random test

On 10/20/2017 02:30 AM, Sergey wrote: > > I believe the problem can be not related to RAM space, since today I > run into the same issue on 200GB RAM machine. Awesome! You've found a bug with either cassandra-dtest or cassandra. Welcome to Apache Cassandra Test Engineering. :) -- Kind regards,

Re: Somewhat Weekly Cassandra Dev Wrapup

On 10/31/2017 07:17 PM, kurt greaves wrote: > It's usually pretty clear what is a fix in the changes log but they > definitely require checking. However I'd say putting more boilerplate in > the changes log isn't really necessary and would be hard to enforce. If we > could generate a report with th

Re: Flakey Dtests

The `test-cdc` target is not a dependent of `test-all`, so it was set up as a separate job in Jenkins: https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-3.11-test-cdc/ https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-trunk-test-cdc/ -- Michael On 11/27/2017 03:45 PM,

Re: Cassandra Dtests: skip upgrade tests

Yep, that rm is a bit of a hack, since environment vars for JDK{8,9}_HOME are not able to be set on the static slaves. The "proper" way to skip them is just a normal nose exclude (drop --collect-only to actually run 'em): ./run_dtests.py --nose-options="--collect-only -e upgrade_tests/" or noset

Re: create branch in my github account

On 01/30/2018 03:47 PM, Tyagi, Preetika wrote: > Hi all, > > I'm working on the JIRA ticket CASSANDRA-13981 and pushed a patch > yesterday, however, I have been suggested to create a branch in my > github account and then push all changes into that. The patch is too > big hence this seems to be a

Re: create branch in my github account

On 01/30/2018 04:03 PM, Michael Shuler wrote: > > You could do this in your fork on the trunk repository, but it's You could do this in your fork on the trunk *branch*, but... - apologies for mixing terms, while trying to be clear and helpful about terminology :)

[VOTE] Release Apache Cassandra 2.1.20

I propose the following artifacts for release as 2.1.20. sha1: b2949439ec62077128103540e42570238520f4ee Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.20-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1152/org/apac

[VOTE] Release Apache Cassandra 2.2.12

I propose the following artifacts for release as 2.2.12. sha1: 1602e606348959aead18531cb8027afb15f276e7 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.12-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1153/org/apac

[VOTE] Release Apache Cassandra 3.0.16

I propose the following artifacts for release as 3.0.16. sha1: 91e83c72de109521074b14a8eeae1309c3b1f215 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.16-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1154/org/apac

[VOTE] Release Apache Cassandra 3.11.2

I propose the following artifacts for release as 3.11.2. sha1: f6ec5c5d18c2900af0ef6e314edbd19aaa682a55 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.2-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1155/org/apac

[VOTE VETOED] Release Apache Cassandra 3.11.2

On 02/12/2018 04:53 PM, kurt greaves wrote: > May as well just recut and include it IMO. Sure, the issue is > work-aroundable, but in a pretty terrible way. Only a few hours will be > lost (sorry Michael :/)​ Veto by myself, based on the previous comments. I've deleted the 3.11.2-tentative pointi

[VOTE] (Take 2) Release Apache Cassandra 3.11.2

I propose the following artifacts for release as 3.11.2. sha1: 8a5e88f635fdb984505a99a553b5799cedccd06d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.2-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1156/org/apac

Re: CASSANDRA-14183 review request -> logback upgrade to fix CVE

I tried a logback 1.2.x jar update a number of months ago to fix the broken log rotation (try setting rotation to a large number - you'll find you only get I think it was 10 files, regardless of setting). Like we've found updating other jars in the past, this seemingly "simple" update broke a numb

[VOTE FAILED] (Take 2) Release Apache Cassandra 3.11.2

Thanks for all the feedback on this tentative release commit. Commit 1d506f9 (current cassandra-3.11 branch HEAD) just passed testall 100% for me in CI, so I'll get a new artifact set up soon for Take 3. -- Warm regards, Mcihael On 02/14/2018 07:30 AM, Jason Brown wrote: > CASSANDRA-14234 (whic

[VOTE FAILED] Release Apache Cassandra 3.0.16

an you >>> include >>>> it in the future [VOTE] emails? >>>> >>>> Thanks, >>>> >>>> -Jason >>>> >>>> >>>> >>>> On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad wrote: >>>> >&

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

On 02/14/2018 11:40 AM, Michael Shuler wrote: > Thanks for the feedback on 3.0.16 tentative release. > > Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test > (in both standard and -compression suites) in CI for me. This test has > failed 20 times in the las

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

chael On 02/14/2018 11:44 AM, Michael Kjellman wrote: > i looked at this a few weeks back. this is asf jenkins right? if so, it’s a > permissions issue on the build executors > >> On Feb 14, 2018, at 9:40 AM, Michael Shuler wrote: >> >> Thanks for the feedback on 3.0.

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

ork locally and in the cassandra-test > docker image. > > given everyone can partake on circleci runs and asf jenkins i think we should > send out those links and base the vote off those runs. > >> On Feb 14, 2018, at 9:48 AM, Michael Shuler wrote: >> >> Thi

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

ng the old circleci 1.0 based config. > >> On Feb 14, 2018, at 10:16 AM, Michael Shuler wrote: >> >> So far, I have had very unpredictable test runs from CirceCI and ASF >> Jenkins. Commit 890f319 resulted in 4 completely different test failures >> for me today in

[VOTE] (Take 2) Release Apache Cassandra 3.0.16

I propose the following artifacts for release as 3.0.16. sha1: 890f319142ddd3cf2692ff45ff28e71001365e96 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.16-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1157/org/apac

[VOTE] (Take 3) Release Apache Cassandra 3.11.2

I propose the following artifacts for release as 3.11.2. sha1: 1d506f9d09c880ff2b2693e3e27fa58c02ecf398 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.2-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1158/org/apac

Re: [VOTE] (Take 2) Release Apache Cassandra 3.0.16

On 02/15/2018 11:49 AM, Josh McKenzie wrote: > What would it take for us to get green utest/dtests as a blocking part of > the release process? i.e. "for any given SHA, here's a link to the tests > that passed" in the release vote email? Jason graciously linked to his passing test-all runs for thi

[VOTE PASSED] Release Apache Cassandra 2.1.20

With 9 binding +1 and no other votes, the 2.1.20 release passes. I will get the artifacts uploaded today. -- Kind regards, Michael On 02/12/2018 02:30 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.20. > > sha1: b2949439ec62077128103540e42570238520f

[VOTE PASSED] Release Apache Cassandra 2.2.12

With 10 binding +1, 1 non-binding +1, and no other votes, this vote for 2.2.12 passes. I'll upload the artifacts today. -- Kind regards, Michael On 02/12/2018 02:30 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.12. &

[RELEASE] Apache Cassandra 2.1.20 released - PLEASE READ NOTICE

PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092) -- The maximum expiration timestamp that can be represented by the storage engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL thatl expire after thi

[RELEASE] Apache Cassandra 2.2.12 released - PLEASE READ NOTICE

PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092) -- The maximum expiration timestamp that can be represented by the storage engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL thatl expire after thi

[VOTE PASSED] (Take 2) Release Apache Cassandra 3.0.16

With 5 binding +1, 2 non-binding +1, and no other votes, this release has passed. I will get 3.0.16 uploaded as soon as I can! -- Kind regards, Michael On 02/14/2018 02:40 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.16. >

[VOTE PASSED] (Take 3) Release Apache Cassandra 3.11.2

I count 6 binding +1, 1 non-binding +1, and no other votes for this release of 3.11.2. I will get the artifacts uploaded shortly. -- Kind regards, Michael On 02/14/2018 03:09 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.2. >

[RELEASE] Apache Cassandra 3.0.16 released - PLEASE READ NOTICE

PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092) -- The maximum expiration timestamp that can be represented by the storage engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL thatl expire after thi

[RELEASE] Apache Cassandra 3.11.2 released - PLEASE READ NOTICE

PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092) -- The maximum expiration timestamp that can be represented by the storage engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL thatl expire after thi

Re: CREATE INDEX without IF NOT EXISTS when snapshoting

Double check your patches apply cleanly to the current branch HEADs, since they are a few months old (CHANGES.txt conflicts and any others you find) and update patches. You're doing the right thing asking for a reviewer/committer to get a little attention. Conflict-free patches help that person. I

Re: [DISCUSS] java 9 and the future of cassandra on the jdk

As I mentioned in IRC and was pasted earlier in the thread, I believe the easiest path is to follow the major releases of OpenJDK in the long-term-support Linux OS releases. Currently, Debian Stable (Stretch), Ubuntu 16.04 (Bionic (near release)), and Red Hat / CentOS 7 all have OpenJDK 8 as the de

Re: [DISCUSS] java 9 and the future of cassandra on the jdk

On 03/22/2018 05:30 PM, Michael Shuler wrote: > Ubuntu 16.04 (Bionic (near release)) Ubuntu 18.04 (Bionic) :) Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: de

Re: Roadmap for 4.0

On 04/03/2018 03:51 PM, Nate McCall wrote: >> My concrete proposal would be to declare a feature freeze for 4.0 in 2 >> months, >> so say June 1th. That leave some time for finishing features that are in >> progress, but not too much to get derailed. And let's be strict on that >> freeze. > > I qu

Re: Roadmap for 4.0

On 04/04/2018 07:06 PM, Nate McCall wrote: > > It feels to me like we are coalescing on two points: > 1. June 1 as a freeze for alpha > 2. "Stable" is the new "Exciting" (and the testing and dogfooding > implied by such before a GA) > > How do folks feel about the above points? +1 +1 :) Michael

Re: Roadmap for 4.0

On 04/05/2018 12:32 PM, Josh McKenzie wrote: > Just as a matter of perspective, I'm personally mentally diffing from > when 3.0 hit, not 3.10. > >> commit 96f407bce56b98cd824d18e32ee012dbb99a0286 >> Author: T Jake Luciani >> Date: Fri Nov 6 14:38:34 2015 -0500 >> 3.0 release versions > >

Re: Roadmap for 4.0

Our current internal trunk test summary is attached. We're actually in a pretty good state on the baseline test suites, thanks to committers/reviewers. Due to compute resource limitations and error noise on py2->py3 update, the following test suites are not being run internally on our CI system, s

Re: Roadmap for 4.0

On 04/12/2018 10:57 AM, Michael Shuler wrote: > Our current internal trunk test summary is attached. We're actually in a > pretty good state on the baseline test suites, thanks to > committers/reviewers. > > Due to compute resource limitations and error noise on py2->py3

Re: Evolving the client protocol

This is purely my own opinion, but I find the use of the term 'shard' quite unfortunate in the context of a distributed database. The historical usage of the term has been the notion of data partitions that reside on separate database servers. There is a learning curve with distributed databases, a

Re: [VOTE] Release Apache Cassandra 5.0-rc1 (take3)

+1 (we're off rhel7, woot!) On 7/17/24 15:20, Mick Semb Wever wrote: On Wed, 17 Jul 2024 at 21:40, Brandon Williams > wrote: On Wed, Jul 17, 2024 at 2:36 PM Mick Semb Wever mailto:m...@apache.org>> wrote: > > Should we remove the noboolean rpm from the

Re: [VOTE] Release test-api 0.0.17

+1 On 9/10/24 09:34, Doug Rohrer wrote: Proposing the test build of in-jvm dtest API 0.0.17 for release Repository: https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git Candidate SHA: https://github.com/ap

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

I've stated this same opinion prior, fix was in NEWS.txt and users had a bad day with a behavior change. Perhaps this kind of inclusion needs more exposure. This is exactly the sort of change may *also* be best stated clearly in the vote/release emails, ala: ==

Re: Are there Cassandra Jenkins server?

On 11/10/2013 08:21 PM, Shinpei Nakata wrote: > I've been working on writing a patch for Cassandra recently on the > latest git trunk > (http://git-wip-us.apache.org/repos/asf/cassandra.git). However, from > last week, I got many unit tests error/failure from 'ant test' result. > I'm wondering that

Re: Are there Cassandra Jenkins server?

On 11/11/2013 08:59 PM, Shinpei Nakata wrote: > On Tue, Nov 12, 2013 at 12:46 AM, Michael Shuler > wrote: >> https://issues.apache.org/jira/browse/CASSANDRA-6321 > > Okay, I relieved. Exactly same failures (TIMEOUT) happening in my > local environment. Shinpei, a fix was

Could .gitignore be added? (was: can test/Test.iml be removed?)

On 12/13/2013 11:28 PM, graham sanderson wrote: This seemed to get introduced (by mistake?) in ef33f9543 Would there be any issues with adding a .gitignore to the repository? I could work one up. -- Kind regards, Michael

Re: [VOTE] Release Apache Cassandra 1.2.13 (Strike 3)

On 12/18/2013 03:46 AM, Sylvain Lebresne wrote: Third time's the charm, I propose the following artifacts for release as 1.2.13. sha1: 1b4c9b45cbf32a72318c42c1ec6154dc1371e8e2 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.13-tentative Artifacts: https://r

Re: Could .gitignore be added?

dd a .gitignore: --- cut here --- .classpath .idea/ .project build/ src/gen-java/ cassandra.iml *.pyc cscope.* *.swp *~ src/resources/org/apache/cassandra/config/ --- cut here --- On Dec 19, 2013, at 2:16 PM, Jonathan Ellis wrote: I can't think of any. On Sat, Dec 14, 2013 at 11:14 AM, M

Re: Could .gitignore be added?

On 12/19/2013 05:46 PM, Jacob Rhoden wrote: Your missing netbeans includes. I also include the following for anything java related. .*.swo Thumbs.db Added. # Maven and other build system/IDE artifacts bin build out/* target/* We can't exclude bin/, since it's under revision control and bu

Re: [VOTE] Release Apache Cassandra 1.2.14

non-binding +1 - unit, distributed, and upgrade testing looks good to me. -- Michael On 01/31/2014 05:33 AM, Sylvain Lebresne wrote: I propose the following artifacts for release as 1.2.14. sha1: 6a9314408cbd69ce26c2ba04bf49df7809a911bf Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.g

Re: [VOTE] Release Apache Cassandra 2.0.5 (Strike 2)

non-binding +1 - looks good to me -- Michael On 02/03/2014 03:07 AM, Sylvain Lebresne wrote: With typo introduced by CASSANDRA-6505 fixed, I propose the following artifacts for release as 2.0.5. sha1: b71372146135fdcee6353ec8254ebfd87c42f907 Git: http://git-wip-us.apache.org/repos/asf?p=cassan

cassandra-2.1 testing

Here is the current state of unit and dtest results for the cassandra-2.1 branch, from the commit I started with this morning. origin/cassandra-2.1 commit 0fa5cba35b9c97ad34dedbbd89a933f5b9d156e9 Date: Tue Apr 8 12:26:09 2014 -0500 Unit Tests Failing: or

Re: cassandra-2.1 testing

On 04/08/2014 03:50 PM, Jonathan Ellis wrote: How many of these are bisect-able? Many are test implementation errors, and may not be directly related to c* errors. They may need to be fixed in ccm or the dtest is just wrong. I'll keep after these tickets, and bisect c* for ones that look like

Re: cassandra-2.1 testing

On 04/08/2014 04:04 PM, Michael Shuler wrote: On 04/08/2014 03:50 PM, Jonathan Ellis wrote: How many of these are bisect-able? Many are test implementation errors, and may not be directly related to c* errors. They may need to be fixed in ccm or the dtest is just wrong. I'll keep after

Re: [VOTE] Release Apache Cassandra 2.0.7

non-binding +1 -- Michael On 04/14/2014 10:38 AM, Sylvain Lebresne wrote: sha1: 7dbbe9233ce83c2a473ba2510c827a661de99400 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.7-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecass

Re: [VOTE] Release Apache Cassandra 2.0.7

On 04/14/2014 05:19 PM, Michael Shuler wrote: non-binding +1 Build/test for the 2.0.7-tentative tag, if anyone wants to dig through the results: http://cassci.datastax.com/job/cassandra-2.0/318/ http://cassci.datastax.com/job/cassandra-2.0_test/308/ http://cassci.datastax.com/job/cassandra

Re: Performance Tickets

On 04/15/2014 08:28 AM, Benedict Elliott Smith wrote: It's only been six months since the last performance drive, and 2.1 is now around the corner. But I'm hoping we can push performance even further for 3.0. With that in mind, I've picked out what I think are the nearest term wins to focus on.

Re: bugs report for 2.0.7

Then you likely need to fix your I/O problem. The most recent error you posted is an EOFException - the file being read ended unexpectedly. Probably when you ran out of disk space. -- Michael On 04/29/2014 07:48 PM, Yatong Zhang wrote: Here is another type of exception, seems all are I/O rela

Re: Cannot subscribe to users mailing list

On 05/12/2014 11:58 AM, Maciej Miklas wrote: I’ve tried to subscribe to user-subscr...@cassandra.apache.org, it takes one day to receive confirmation, and later on nothing - no emails, I’ve been waiting for two days. Could someone check it out? https://blogs.apache.org/infra/entry/mail_outage

Re: Too Many Open Files (sockets) - VNodes - Map/Reduce Job

(this is probably a better question for the user list - cc/reply-to set) Allow more files to be open :) http://www.datastax.com/documentation/cassandra/1.2/cassandra/install/installRecommendSettings.html -- Kind regards, Michael On 06/04/2014 12:15 PM, Florian Dambrine wrote: Hi every body,

Re: [VOTE PASSED] Release Apache Cassandra 1.2.17

It seems a bit of a flaw in our test builds allowed us to miss a problem with this release. Cassandra 1.2.x is intended to remain java_1.6 compatible, to the best of my knowledge. Unfortunately, CASSANDRA-7147 includes a bit of code that breaks the build when using Oracle JDK 1.6. Should this

Re: [VOTE] Release Apache Cassandra 2.0.10

non-binding +1 On 08/08/2014 05:03 AM, Sylvain Lebresne wrote: I propose the following artifacts for release as 2.0.10. sha1: cd37d07baf5394d9bac6763de4556249e9837bb0 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.10-tentative Artifacts: https://repositor

Re: [VOTE CLOSED] Release Apache Cassandra 2.0.10

On 08/11/2014 09:50 AM, horschi wrote: Would it be possible to have CASSANDRA-7511 reviewed also? commit 60eab4e45e18d6b08350187acf56deed9654fda7 Author: Jake Luciani Date: Fri Aug 1 10:30:48 2014 -0400 Fix truncate to always call flush on table Patch by Jeremiah Jordan; reviewed b

Re: [VOTE CLOSED] Release Apache Cassandra 2.0.10

On 08/11/2014 04:21 PM, Michael Shuler wrote: On 08/11/2014 09:50 AM, horschi wrote: Would it be possible to have CASSANDRA-7511 reviewed also? That was committed to the c*-2.0 branch prior to the vote and was in the tentative-2.0.10 CHANGES.txt: * Fix truncate to always flush (CASSANDRA

Re: Error : NoClassDefFoundError: org/apache/cassandra/service/CassandraDaemon

On 10/06/2014 04:36 AM, Vishanth Balasubramaniam wrote: root@instance-0001:/opt/cassandra/bin# cassandra root@instance-0001:/opt/cassandra/bin# Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/cassandra/service/CassandraDaemon Caused by: java.lang.ClassNotFoundExcepti

Re: Reviewing patches

On 11/11/2014 03:35 PM, oded peer wrote: I submitted patches for Cassandra-7304 (a month ago) and for Cassandra-4476 (a week ago). Both patches are waiting to be reviewed. These are my first patches in the Cassandra project. Can anyone explain and how the review process works? How long does it us

Re: Error opening zip file or JAR manifest missing

On 11/22/2014 05:58 PM, Rajanarayanan Thottuvaikkatumana wrote: A huge number of tests are failing with the same error message. Reproducing one of such errors. testlist: [echo] running test bucket 0 tests [mkdir] Created dir: /Users/RajT/cassandra-source/cassandra-trunk/build/test/c

Re: Reviewing patch: CASSANDRA-7882

box/cassandra-dev/201410.mbox/%3CCALdd-zjmvp7JOtguZ_k951RQHDtFt1cthX%3DRnHQ332C%3DgAZbjw%40mail.gmail.com%3E [1] http://wiki.apache.org/cassandra/CodeStyle -- Warm regards, Michael Shuler

Re: Reviewing patch: CASSANDRA-7882

On 12/02/2014 01:04 PM, Michael Shuler wrote: There are currently 64 patches available, which is awesome! ..and unfortunate when they wait for review. The project is aware of the backlog[0] and it takes time to dig through them all. Everyone can help. Since I was looking to see what &quo

"In Progress" JIRA Status

A few JIRA users are using the Start/Stop Progress triggers to show "In Progress" status on tickets, and this has been very useful to ticket watchers. If you have a ticket or two that you are actively working on, even if it is "sort of working on", if you could try to mash the Start/Stop Progre

Re: [VOTE] Release Apache Cassandra 2.1.3

I'm a -1. CASSANDRA-7688 caused this regression: from: http://cassci.datastax.com/job/cassandra-2.1_novnode_dtest/470/testReport/ to: http://cassci.datastax.com/job/cassandra-2.1_novnode_dtest/472/testReport/ -- Michael On 02/09/2015 10:50 AM, Jake Luciani wrote: I propose the following ar

Re: Question on updating Cassandra dependencies

On 03/13/2015 05:58 PM, Joe Fasano wrote: I'm not familiar with opening a JIRA, but would be great to open a general incident for updating all dependencies in 3.0. Just a quick follow up - a JIRA was opened on the topic: https://issues.apache.org/jira/browse/CASSANDRA-8974 On Fri, Mar 13, 20

3.0 and beyond apt repository structure

Will we need to create new 3.0, 3.1, 3.2, ... deb repositories for each monthly release? I'm not intimately familiar with the bintray redirects that ASF Infra set up, recently, but we did have a few issues at first. I'm wondering if this will require a redirect addition request to Infra for eac

Re: [VOTE] Release Apache Cassandra 4.0.0 (third time is the charm)

+1 Kind regards, Michael On 7/22/21 5:40 PM, Brandon Williams wrote: I am proposing the test build of Cassandra 4.0.0 for release. sha1: 902b4d31772eaa84f05ffdc1e4f4b7a66d5b17e6 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.0-tentative Maven Artifacts: ht

Re: [VOTE] Release Apache Cassandra 3.11.11

+1 Kind regards, Michael On 7/25/21 2:06 PM, Brandon Williams wrote: I am proposing the test build of Cassandra 3.11.11 for release. sha1: 4cafe2288e56e1135d65e76adbcd6c2de9306d6b Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.11-tentative Maven Artifacts

Re: [VOTE] Release Apache Cassandra 3.0.25

+1 Kind regards, Michael On 7/25/21 12:40 PM, Brandon Williams wrote: I am proposing the test build of Cassandra 3.0.25 for release. sha1: 06235e93e16d1f483a3b03ba02f8fb29e33305fa Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.25-tentative Maven Artifacts:

Re: [VOTE] CEP-16 - Auth Plugin Support for CQLSH

+1 On 10/11/21 4:47 AM, Stefan Miklosovic wrote: Hi list, based on the discussion thread about CEP-16 (1), I would like to have a vote on that. It seems to me CEP-16 is so straightforward there is more or less nothing to discuss in more depth as the feedback it gathered was mostly formal and n

Re: [VOTE] CEP-15: General Purpose Transactions

1. +1 2. +1 3. +1 On 10/14/21 11:31 AM, bened...@apache.org wrote: Hi everyone, I would like to start a vote on this CEP, split into three sub-decisions, as discussion has been circular for some time. 1. Do you support adopting this CEP? 2. Do you support the transaction semantics proposed by

Cassandra site broken links

(Sending to dev@ which seems a better place to discuss; updated subject. Thanks OP!) I ran a couple link checking tools on the site and there are lots more problems than the couple noted. This seems like a good task for a non-dev to make a substantial project impact. Muffet [0] seemed the qui

Re: Cassandra site broken links

FYI - I'm going to try to slow down the checks, since I just noticed a bunch of the 4xx errors are "HTTP 429 Too Many Requests" Kind regards, Michael On 11/6/21 11:52 AM, Michael Shuler wrote: (Sending to dev@ which seems a better place to discuss; updated subject. Thanks

Re: Cassandra site broken links

rep '^\sid #' c*.log.txt |wc -l 1416 $ egrep '^\s4' c*.log.txt |wc -l 55 $ egrep '^\slookup' c*.log.txt |wc -l 20 $ egrep '^\stimeout' c*.log.txt |wc -l 1 Warm regards, Michael On 11/6/21 11:59 AM, Michael Shuler wrote: FYI - I'm going to try to slow do

Re: [VOTE] CEP-3: Guardrails

+1 Kind regards, Michael Shuler On 11/11/21 5:29 AM, Andrés de la Peña wrote: Hi everyone, I would like to start a vote on this CEP. Proposal: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-3%3A+Guardrails Discussion: https://lists.apache.org/thread

<    1   2   3   4   5   >