Re: Making CommitLog pluggable

kb (or whatever the physical page size is)? Thanks! best, kjellman > On Nov 1, 2017, at 2:40 PM, 大平怜 wrote: > > Hi Michael, > > Yes, testing is always a problem, and that is exactly why we would like to > release > our code as a plugin, outside of the main source tree, s

Re: Pluggable storage engine discussion

Hi, There's a ticket also for columnar storage option, which I guess is something that many might want. Not least because in many cases it could reduce the storage footprint by a large margin (and enable more sophisticated compression options), even if we discount the possible query advantage

Re: Flakey Dtests

here's a pre-Thanksgiving call for help. > > If you haven't been paying attention to JIRA, you likely didn't notice that > Josh went through and triage/categorized a bunch of issues by adding > components, and Michael took the time to open a bunch of JIRAs for faili

Re: Flakey Dtests

broken... Do we have any volunteers to fix the broken Materialized Views and CDC DTests? best, kjellman > On Nov 15, 2017, at 5:59 PM, Michael Kjellman > wrote: > > yes - true- some are flaky, but almost all of the ones i filed fail 100% (💯) > of the time. i look forward to tr

Re: Flakey Dtests

how this is supposed to work? Was handling rpc_port in the upgrade dtests just missed when this was removed for whatever reason from trunk? thanks… best, kjellman On Nov 16, 2017, at 9:09 PM, Michael Kjellman mailto:mkjell...@internalcircle.com>> wrote: Quick update re: dtests and of

Re: Flakey Dtests

? when do ccm releases get published to pypy? On Nov 17, 2017, at 12:18 AM, Michael Kjellman mailto:mkjell...@internalcircle.com>> wrote: I see a ton of upgrade tests right now failing for: Unexpected error in node1 log, error: ERROR [main] 2017-11-17 07:57:54,477 CassandraDaemon.ja

Re: CCM dependency in dtests

thanks for driving this Stefan this is definitely an issue that I recently saw too trying to get all the dtests passing. having logic you need to fix in 3 repos isn’t ideal at all. > On Nov 27, 2017, at 4:05 AM, Stefan Podkowinski wrote: > > Just wanted to bring a recent discussion about

Re: Flakey Dtests

y to take a look at the CDC tests next week; looks like one of the > base unit tests is failing as well. > > On Fri, Nov 17, 2017 at 12:09 AM, Michael Kjellman < > mkjell...@internalcircle.com> wrote: > >> Quick update re: dtests and off-heap memtables: >> >>

Re: Flakey Dtests

n't been paying attention to JIRA, you likely didn't notice that Josh went through and triage/categorized a bunch of issues by adding components, and Michael took the time to open a bunch of JIRAs for failing tests. How many is a bunch? Something like 35 or so just for tests currently

Re: Flakey Dtests

better. best, kjellman On Nov 27, 2017, at 2:43 PM, Michael Kjellman mailto:mkjell...@internalcircle.com>> wrote: (with 100 containers we can actually build the project, run all of the unit tests, and run all of the dtests in roughly 28 minutes!).

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: Flakey Dtests

do you know why this is the case? shouldn’t -all test...all? > On Nov 27, 2017, at 7:39 PM, Michael Shuler wrote: > > 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

[PROPOSAL] Migrate to pytest from nosetests for dtests

I'd like to propose we move from nosetest to pytest for the dtests. It looks like nosetests is basically abandoned, the python community doesn't like it, it hasn't been updated since 2015, and pytest even has nosetests support which would help us greatly during migration (https://docs.pytest.or

Re: [PROPOSAL] Migrate to pytest from nosetests for dtests

bug or > restriction getting in the way? > >> On Tue, Nov 28, 2017 at 8:34 PM, Jon Haddad wrote: >> >> +1 >> >> I stopped using nose a long time ago in favor of py.test. It’s a >> significant improvement. >> >>> On Nov 28, 2017, at 10:

Re: [PROPOSAL] Migrate to pytest from nosetests for dtests

s/handling/hanging > On Nov 29, 2017, at 9:54 AM, Michael Kjellman > wrote: > > i keep seeing nose randomly handing after a test successfully completes > execution. i’m very far from a python guru but i spent a few hours with gdb > trying to debug the thing and get pyt

Re: CCM dependency in dtests

Hey Stefan, any updates on this? Thanks. best, kjellman > On Nov 27, 2017, at 7:34 AM, Michael Kjellman > wrote: > > thanks for driving this Stefan this is definitely an issue that I > recently saw too trying to get all the dtests passing. having logic you need > to fi

Re: Cassandra Dtests: skip upgrade tests

upgrade_tests/" or nosetests --collect-only -e upgrade_tests/ Also, to run only the upgrade_tests, since we're here :) ./run_dtests.py --nose-options="--collect-only upgrade_tests/" or nosetests --collect-only upgrade_tests/ -- Michael On 12/08/2017 12:07 PM, Jay Zhuan

Re: Test patch to Cassandra.3.0.15 using dtests

i’ve been working on a story to improve this around the clock. including better documentation (and a —help flag with options to make it easy to know how to run dtests and a few runtime sanity checks about the environment)! stay tuned! > On Dec 13, 2017, at 3:24 AM, Sergey wrote: > > Hi! > > I

[Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

I just created https://issues.apache.org/jira/browse/CASSANDRA-14134 which includes tons of details (and a patch available for review) with my efforts to migrate dtests from nosetest to pytest (which ultimately ended up also including porting the ode from python 2.7 to python 3). I'd love if pe

Re: Cassandra Dtests: skip upgrade tests

single flag (easily discoverable in the —help) will turn them on if necessary. or you can use the power features of pytest collection filtering when invoking pytest directly (look at the -m option). hope this helps going forward!! best, kjellman On Dec 8, 2017, at 2:03 PM, Michael Shuler

Re: Test patch to Cassandra.3.0.15 using dtests

casual contributor make a change and run the unit and dtests against their branch in circleci (using just a free circleci OSS account) without any end user effort! best, kjellman On Dec 13, 2017, at 12:28 PM, Michael Kjellman mailto:mkjell...@internalcircle.com>> wrote: i’ve been workin

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

testable in parallel. yes, i didn't touch cassandra-builds yet.. focused on getting circleci and local runs working first... once we're happy with that and stable we can make the changes to jenkins configs pretty easily... > > > > On 21.12.2017 11:13, Michael Kjellman wrote:

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

I reproduced the NOTSET log issue locally... got a fix.. i'll push a commit up in a moment. > On Jan 2, 2018, at 11:24 AM, Michael Kjellman > wrote: > > Comments Inline: Thanks for giving this a go!! > >> On Jan 2, 2018, at 6:10 AM, Stefan Podkowinski wrote: >

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

y and do we have > to do the same for jenkins? > > >> On 02.01.2018 22:42, Michael Kjellman wrote: >> I reproduced the NOTSET log issue locally... got a fix.. i'll push a commit >> up in a moment. >> >>> On Jan 2, 2018, at 11:24 AM, Michael Kjel

Re: Question on submitting a patch

great question! i personally always just leave everything blank to effectively just get the stupid state changed reason number 3000 why I personally hate JIRA. > On Jan 5, 2018, at 12:44 PM, Tyagi, Preetika wrote: > > Hi all, > > When I click on "Submit Patch" option, it pops up a new scr

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

install instructions to figure out what could be improved on. any existing behavior i’ve inadvertently now removed that’s going to make someone’s life miserable? 😅 thanks! looking forward to hearing any and all feedback from the community! best, kjellman On Jan 3, 2018, at 8:08 AM, Michael

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

reliable is super huge. There >> are a lot of folks in our community who are not well versed with >> python (myself included). I wholly support *any* efforts we can make >> for the dtest process to be easy. >> >> Thanks a bunch for taking this on. I think it will pay

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

e for dtests. Yours seem to be running on xlarge. On 10.01.18 21:05, Michael Kjellman wrote: plan of action is to continue running everything on asf jenkins. in additional all developers (just like today) will be free to run the unit tests and as many of the dtests as possible against their local te

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

at 1:53 PM, Michael Kjellman > wrote: > > i had done some limited testing on the medium size an didn't see quite as bad > behavior you were seeing... :\ > > i added a test fixture > (sufficient_system_resources_for_resource_intensive_tests) that just > currently d

Re: URGENT: CASSANDRA-14092 causes Data Loss

why are people inserting data with a 15+ year TTL? sorta curious about the actual use case for that. > On Jan 25, 2018, at 12:36 PM, horschi wrote: > > The assertion was working fine until yesterday 03:14 UTC. > > The long term solution would be to work with a long instead of a int. The > seri

Re: create branch in my github account

d. It is very common to have a number of remotes configured in your local repository: one for your fork, one for the apache upstream, ones for other user's forks, etc. If you do your work directly in your trunk branch, you'll have conflicts when pulling in new commits from apache/cassandr

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 :)

Re: cpp driver warning for create keyspace statement

data center name during the keyspace creation; however that is to be expected since that data center would not exist or be known to the cluster. ~Fero Michael Fero

[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.

[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

from 1.1.3 to 1.2.3, so I do not wish to break other user's applications, as I have experienced. I do not think this should block the current releases, unless someone wants to do some significant testing and user outreach for tentatively breaking their applications. -- Michael On 02/13/2

[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

, since we're here? :) -- Kind regards, Michael On 02/14/2018 07:30 AM, Jason Brown wrote: > I think we can attempt another build and vote now. > > On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown wrote: > >> CASSANDRA-14219 is committed and tests look clean (https://circle

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

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.16 tentative release. > > Commit 890f319 (current cassandra-3.0 branch H

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

This is an internal Jenkins instance that's not reachable on the internet. What's the permissions issue? The test runs on this internal instance are exactly the way cassci used to run - launch a scratch machine, check out, build, run tests. I'll see if I can repro locally. Mi

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

runs. > On Feb 14, 2018, at 9:48 AM, Michael Shuler wrote: > > This is an internal Jenkins instance that's not reachable on the internet. > > What's the permissions issue? The test runs on this internal instance > are exactly the way cassci used to run - launch a

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

. I'm fine with cutting a new release set from 890f319 and chalking this up to test flakiness. -- Kind regards, Michael On 02/14/2018 11:50 AM, Michael Kjellman wrote: > the tests are writing something to java.io.tmpdir which for whatever reason > isn’t writable. the same exact tests w

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

please use the latest circleci config that is in trunk. looking at the config you used in your run you’re using 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 > Jen

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

I apologize for being naive. The test runs do not come from the in-tree circle.yml file and I need to do something different? On 02/14/2018 12:21 PM, Michael Kjellman wrote: > please use the latest circleci config that is in trunk. looking at the config > you used in your run you’re usi

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

com/apache/cassandra/blob/trunk/.circleci/config.yml FYI: kjellman/cassandra-test:0.4.3 is was built from the Docker file as committed here: https://github.com/mkjellman/cassandra-test-docker/blob/master/Dockerfile best, kjellman On Feb 14, 2018, at 10:24 AM, Michael Shuler mailto:mich...@pban

[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

t; is super valuable. I could do it all myself for releases, but then I'm doing it all.. I'm all for voting with your test results and we rally around fixing the last few things together. This was rather enjoyable, even though it took a few tries, but there are multiple people running te

[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

Re: Cassandra Needs to Grow Up by Version Five!

hi ken, sorry you don’t like the database. some thoughts: 1) please file actionable jiras for places you feel need to be improved in the database... this is the best way to make and encourage the change you’re looking for. it seems you have quite a few ideas from your post that could be broken

Re: Cassandra Needs to Grow Up by Version Five!

that you’d personally like to see prioritized - and advocate to have resources allocated towards implementing and ultimately get those scheduled for a release over other ones. best, kjellman > On Feb 18, 2018, at 11:07 PM, Kenneth Brotman > wrote: > > Hi Michael, actually I do ve

[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: Cassandra Needs to Grow Up by Version Five!

kenneth: could you please send your jira information? i'm unable to even find an account on http://issues.apache.org with your name despite multiple attempts. thanks! best, kjellman > On Feb 21, 2018, at 2:20 PM, Kenneth Brotman > wrote: > > Jon, > > Very sorry that you don't see the value

Re: Cassandra Needs to Grow Up by Version Five!

Please do send them! There was a *lot* of really hard great work by a lot of people over the past year to significantly improve the documentation in tree. http://cassandra.apache.org/doc/latest/ https://github.com/apache/cassandra/tree/trunk/doc I still didn't see a reply from you re: my request

Expensive metrics?

Hi, I wanted to get some input from the mailing list before making a JIRA and potential fixes. I'll touch the performance more on latter part, but there's one important question regarding the write latency metric recording place. Currently we measure the writeLatency (and metric write sampler

Re: Expensive metrics?

o how we do threading in 4.0. It's probably also worth opening a JIRA and investigating the calls to nano time. We at least need microsecond resolution here, and there could be something we haven't thought of? It's worth a look at least. Thanks, Blake On 2/22/18, 6:10 AM, "M

Re: Expensive metrics?

or changes to how we do threading in 4.0. It's probably also worth opening a JIRA and investigating the calls to nano time. We at least need microsecond resolution here, and there could be something we haven't thought of? It's worth a look at least. Thanks, Blake On 2/22/18,

Re: Why isn't there a separate JVM per table?

it's an interesting idea. i'd wonder how much overhead you'd end up with message parsing and negate any potential GC wins. rick branson had played around a bunch with running storage nodes and doubling down on the old "fat client" model. if you had 1 tables (yes, barely works but we don't e

Re: Timeout unit tests in trunk

hey dikang: just chatted a little bit about this. proposal: let's add the equivalent of @resource_intensive to unit tests too.. and the first one is to stop from running the MV unit tests in the free circleci containers. thoughts? also, might want to bug your management to see if you can get som

Re: Timeout unit tests in trunk

, Michael Kjellman mailto:kjell...@apple.com>> wrote: hey dikang: just chatted a little bit about this. proposal: let's add the equivalent of @resource_intensive to unit tests too.. and the first one is to stop from running the MV unit tests in the free circleci containers. thoughts?

Fwd: Action Required: We are sunsetting CircleCI 1.0 on August 31, 2018

FYI: we're already fully on circleci 2.0 for the 3.0, 3.11, and trunk branches so no action required for us here! best, kjellman Begin forwarded message: From: The CircleCI Team mailto:no-re...@circleci.com>> Subject: Action Required: We are sunsetting CircleCI 1.0 on August 31, 2018 Date: Febr

Re: Timeout unit tests in trunk

it it into two or multiple tests? > > On Tue, Feb 27, 2018 at 1:32 PM, Michael Kjellman > wrote: > >> well, turns out we already have a jira tracking the MV tests being broken >> on trunk. they are legit broken :) thanks jaso >> >> https://issues.apache.org/

Re: Action Required: We are sunsetting CircleCI 1.0 on August 31, 2018

e, but is this also true > for those branches? > > On 27 February 2018 at 22:58, Michael Kjellman wrote: > >> FYI: we're already fully on circleci 2.0 for the 3.0, 3.11, and trunk >> branches so no action required for us here! >> >> best, >> kjellman

Re: Expensive metrics?

2:25 AM, Nate McCall wrote: Hi Micke, There is some good research in here - have you had a chance to create some issues in Jira from this? On Fri, Feb 23, 2018 at 6:28 AM, Michael Burman wrote: Hi, I was referring to this article by Shipilev (there are few small issues forgotten in that url

Re: CREATE INDEX without IF NOT EXISTS when snapshoting

erson. It does look like a pretty simple change, so keep asking. Bonus points for circle-ci tests completed, etc. :) -- Kind regards, Michael On 03/09/2018 10:19 AM, Javier Canillas wrote: > Guys, > > Hope you are all doing fine. Is there any news about this trivial issue > <https

Re: Debug logging enabled by default since 2.2

ive never understood this change. and it’s been explained to me multiple times. DEBUG shouldn’t run by default in prod. and it certainly shouldn’t be enabled by default for users. but hey, what do i know! just my 2 cents. > On Mar 17, 2018, at 10:55 AM, J. D. Jordan wrote: > > We went throug

Re: Debug logging enabled by default since 2.2

+1. this is how it works. your computer doesn’t run at debug logging by default. your phone doesn’t either. neither does your smart tv. your database can’t be running at debug just because it makes our lives as engineers easier. > On Mar 18, 2018, at 5:14 AM, Alexander Dejanovski > wrote: >

Re: Debug logging enabled by default since 2.2

for our users. > On Mar 18, 2018, at 11:21 AM, Jonathan Ellis wrote: > > That really depends on whether you're judicious in deciding what to log at > debug, doesn't it? > > On Sun, Mar 18, 2018 at 12:57 PM, Michael Kjellman > wrote: > >> +1. th

Re: Debug logging enabled by default since 2.2

first place. > On Mar 18, 2018, at 11:24 AM, Michael Kjellman wrote: > > it’s too easy to make a regression there. and does anyone even have a splunk > (or equivalent) infrastructure to actually keep debug logs around for a long > enough retention period to even have them be help

Re: Debug logging enabled by default since 2.2

up to reviewers and committers to understand the impact of and rules > around the use of different log levels. Said reviewers and committers should > teach new contributors those rules during reviews if they are violated. > > -Jeremiah > >> On Mar 18, 2018, at 2:31 PM, M

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

On 03/21/2018 04:52 PM, Josh McKenzie wrote: This would certainly mitigate a lot of the core problems with the new release model. Has there been any public statements of plans/intent with regards to distros doing this? Since the latest official LTS version is Java 8, that's the only one with pu

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

usiness of keeping users updated with upstream releases of Java, so there's no reason not to utilize them. Michael On 03/22/2018 05:12 PM, Jason Brown wrote: > See the legal-discuss@ thread: > https://mail-archives.apache.org/mod_mbox/www-legal-discuss/201803.mbox/browser >

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

. Apache Cassandra 2.1 is supported until 4.0 release (date TBD) with critical fixes only. -- Kind regards, Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Roadmap for 4.0

folks feel about the above points? +1 +1 :) Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Roadmap for 4.0

ixes only**. The latest release is {{ "2.1" | full_release_link }}. Older (unsupported) versions of Cassandra are [archived here](http://archive.apache.org/dist/cassandra/). -- Warm regards, Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Roadmap for 4.0

Just wanted to throw this out there for some context. There is certainly some work to be done, but I don't think we're in such dire straights as may be assumed from the conversation. -- Kind regards, Michael - To un

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

databases, and I can foresee the use of the term adding additional confusion for new users. Not a fan. -- Kind regards, Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-m

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

onvey what operators need to know, wherever we can, if we include the fix. Link to NEWS.txt is insufficient in this sort of case. Warm regards, Michael On 9/12/24 13:16, Abe Ratnofsky wrote: Expressing another vote in favor of rejection-by-default. If a user doesn't want to lose sleep for

Cassandra not applying keyspace updates

Hello, We are in the process of upgrading out cassandra installation from a single instance to a 6 node cluster with a replication factor of 3. We are using Cassandra 1.1.2. This is something I've done before in other environments, but now I've hit an interesting issue. The cluster has been

Re: max_compaction_threshold removed - bad move

Yikes. Please would be nice.. Also, Sylvian already said they would update the documentation. As a developer, who hasn't forgotten to update documentation? On 1/9/13 8:07 AM, "Radim Kolar" wrote: >if this was renamed then update your documentation: > >http://www.datastax.com/docs/1.2/configura

Re: [VOTE] Release Apache Cassandra 1.2.1

+1 On Jan 24, 2013, at 11:54 PM, "Sylvain Lebresne" wrote: > That list of changes since 1.2.0 is getting pretty long, time to ship that > to > users. I propose the following artifacts for release as 1.2.1. > > sha1: 8540974dbd26989b1cd72608b06e57ebe053bf38 > Git: > http://git-wip-us.apache.org/

Re: Proposal: require Java7 for Cassandra 2.0

7's early releases (and I guess allow but maybe warn for OpenJDK7?). My 2-cents. Best, Michael On 2/6/13 2:21 PM, "Jonathan Ellis" wrote: >Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 >comes out (July). Anecdotally, a bunch of people are running

Re: Understanding the Cassandra Code Base

Discussed in the users list on 1/23/13 http://mail-archives.apache.org/mod_mbox/incubator-cassandra-user/201301.mb ox/%3c11d9ef3eb41c401880e02e51269ea...@portico.io%3E On 2/8/13 2:23 PM, "Rahman, Muntasir Raihan" wrote: >Thanks. I will start from there. > >Muntasir. > >-Original Message

Re: [VOTE] Release Mojo's Cassandra Maven Plugin 1.2.0-1

Considering that 1.2.1 is out, and looking at your project very quickly (looks interesting)/overlaps a bit with CCMBridge no?/ I'd def say +1 :) From: Stephen Connolly mailto:stephen.alan.conno...@gmail.com>> Reply-To: "u...@cassandra.apache.org" mailto:u...@ca

Re: [VOTE] Release Apache Cassandra 1.2.2

+1 On 2/20/13 4:01 PM, "Sylvain Lebresne" wrote: >We've fixed a fair amount of important fixes since 1.2.1 so I propose the >following artifacts for release as 1.2.2. > >sha1: 068b53dd5de928fd80815b54963af796f51f1c38 >Git: >http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs

<    1   2   3   4   5   6   7   >