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

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

+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

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

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

, 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?

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

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!

ichael. > 5) I'm an individual. I am not working at a big company at the moment > Michael. > > Best, > Kenneth Brotman > > > -Original Message- > From: Michael Kjellman [mailto:kjell...@apple.com] > Sent: Sunday, February 18, 2018 10:18 PM &

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: [VOTE FAILED] Release Apache Cassandra 3.0.16

djelly.org>> wrote: 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: [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

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

scratch machine, check > out, build, run tests. > > I'll see if I can repro locally. > > Michael > >> 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

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 HEAD) fails only

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

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.g. 3.5? Do I have to use 3.6 as well locally 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 Kjellm

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

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

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: 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: Cassandra Dtests: skip upgrade tests

As part of the work i did for https://issues.apache.org/jira/browse/CASSANDRA-14134, one of the things I did was add a new command line argument “--execute-upgrade-tests”. all the upgrade tests are now annotated with an upgrade_test pytest annotation. by default they aren’t run. adding a single

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

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

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

/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, Michael Kjellman wrote: >> Hey Jay: >> >> Thanks!! I just took a quick look at the JIRA and noticed th

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

Complicated question unfortunately — and something we’re actively working on improving: Cassci is no longer being offered/run by Datastax and so we've need to come up with a new solution, and what that ultimately is is still a WIP — it’s loss was very huge obviously and a testament to the aweso

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

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

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

yes - true- some are flaky, but almost all of the ones i filed fail 100% (💯) of the time. i look forward to triaging just the remaining flaky ones (hopefully - without powers combined - by the end of this month!!) appreciate everyone’s help - no matter how small... i already personally did a fe

Re: Making CommitLog pluggable

> https://github.com/ppc64le/capi-rowcache > We would just like to repeat this approach in CommitLog. > > > Thanks, > Rei Odaira > > > 2017-11-01 16:30 GMT-05:00 Michael Kjellman : > >> Rei: >> >> One thing that comes up when these type of conv

Re: Making CommitLog pluggable

Rei: One thing that comes up when these type of conversations occur is how the project can test hardware dependent code. In the case of the PPC64 stuff, hardware actually got donated to the ASF so Jenkins runs could be done to check that things work. Any thoughts on this aspect? Might be a bit

Re: Making CommitLog pluggable

I think pluggable commit log is a great idea if we can do it right! 😃 *Especially* given the intent here seems to be motivated by improving endurance and performance on the given storage you're running C* on. We've actually been looking at commit log a bunch recently and doing a pretty deep dive

Re: Integrating vendor-specific code and developing plugins

That’s epic Jeff. Very cool. Sent from my iPhone On May 18, 2017, at 10:28 AM, Jeff Jirsa mailto:jji...@gmail.com>> wrote: On Mon, May 15, 2017 at 5:25 PM, Jeremiah D Jordan < jeremiah.jor...@gmail.com> wrote: To me testable means that we can run the tests a

Re: Dropped Mutation and Read messages.

This discussion should be on the C* user mailing list. Thanks! best, kjellman > On May 11, 2017, at 10:53 AM, Oskar Kjellin wrote: > > That seems way too low. Depending on what type of disk you have it should be > closer to 1-200MB. > That's probably causing your problems. It would still take

Re: Does partition size limitation still exists in Cassandra 3.10 given there is a B-tree implementation?

I'm almost done with a rebased trunk patch. Hit a few snags. I want nothing more to finish this thing... The latest issue was due to range tombstones and the fact that the deletion time was being stored in the index from 3.0 onwards. I hope to have everything pushed very shortly. Sorry for the d

Re: unsubscribe

http://apache.org/foundation/mailinglists.html Sent from my iPhone On Apr 6, 2017, at 9:57 AM, Nitija Patil mailto:nitij...@gmail.com>> wrote: unsubscribe On Thu, Apr 6, 2017 at 10:25 PM, Vineet Gadodia mailto:gadodi...@gmail.com>> wrote: unsubscribe On Wed, Apr 5, 2017 at 1:51 AM, Ksawery

Re: Upgrade the jna version to 4.3.0

Amit – What changes/bug fixes specifically are you looking for in JNA 4.3.0? Thanks! best, kjellman Sent from my iPhone > On Mar 5, 2017, at 12:58 PM, Jason Brown wrote: > > Hi Amit, > > Can you open a Jira for that? Also we can figure out which branches to > target for the upgrade on the Ji

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

Jason has asked for review and feedback many times. Maybe be constructive and review his code instead of just complaining (once again)? Sent from my iPhone > On Nov 19, 2016, at 1:49 PM, Edward Capriolo wrote: > > I would say start with a mindset like 'people will run this in production' > not

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

Honest question: are you *ever* positive Ed? Maybe give it a shot once in a while. It will be good for your mental health. Sent from my iPhone > On Nov 19, 2016, at 11:50 AM, Edward Capriolo wrote: > > This is especially relevant if people wish to focus on removing things. > > For example,

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

Yes, We hit this as well. We have a internal patch that I wrote to mostly revert the behavior back to ByteBuffers with as small amount of code change as possible. Performance of our build is now even with 2.0.x and we've also forward ported it to 3.x (although the 3.x patch was even more complic

Re: Review of Cassandra actions

Thanks Jeff for your thoughtful comments. +100 Sent from my iPhone > On Nov 5, 2016, at 6:26 PM, Jeff Jirsa wrote: > > I hope the other 7 members of the board take note of this response, > and other similar reactions on dev@ today. > > When Datastax violated trademark, they acknowledged it and

Re: DataStax role in Cassandra and the ASF

eatures already in releases for people to adopt so we've got the "features" thing under control for at least a year in my opinion. best, kjellman Sent from my iPhone > On Nov 4, 2016, at 10:33 AM, Michael Kjellman > wrote: > > "Avalon. The database

Re: DataStax role in Cassandra and the ASF

"Avalon. The database" yes autocorrect. That's exactly what I wanted. That should read "scaling the database and stability." Sorry. I'm typing this while walking up a big ass hill in San Francisco heading to the office. 😜 Sent from my iPhone > On Nov 4, 20

Re: Moderation

gt; for the Apache Cassandra PMC and community to reply as well. > > Cheers, > Chris > > >> On 2016-11-04 10:14 (-0700), Michael Kjellman >> wrote: >> @Chris: instead of promoting the arguing going on on this thread could you >> please help lead by examp

Re: DataStax role in Cassandra and the ASF

Hi Kelly- I can't speak to many of your questions as it's not my position to do so. What I can say is that at Apple we are doubling down on open source. We have tons of code in flight -- really big ones in fact -- many already out for review. Our list of enhancements we want to do grows all the

Re: Moderation

@Chris: instead of promoting the arguing going on on this thread could you please help lead by example and reply to Kelly's questions in her email? Thanks. I don't enjoy watching a community I care about continue to explode in front of my eyes ☹️ best, kjellman Sent from my iPhone > On Nov

Re: 8099 Storage Format Documentation as used with PRIMARY_INDEX

Ugh, just finally figured the "header" bit of my question out. Mega lame. :\ > On Oct 18, 2016, at 9:17 AM, Michael Kjellman > wrote: > > I'm working on writing Birch for trunk and I noticed the following: > > https://github.com/apache/cassandra/blob/trunk

Re: Use of posix_fadvise

Sorry, No. Always document your assumptions. I shouldn't need to git blame a thousand commits and read thru a billion tickets to maybe understand why something was done. Clearly thru the conversations on this topic I've had on IRC and the responses so far on this email thread it's not/still not

Re: Use of posix_fadvise

On Tue, Oct 18, 2016 at 11:59 AM, Michael Kjellman < mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com>> wrote: Specifically regarding the behavior in different kernels, from `man posix_fadvise`: "In kernels before 2.6.6, if len was specified as 0, then this was in

Re: Cleanup after yourselves please

Cool, as I would have assumed they would need to be. Given they were initially commented out on 6/30/15 maybe cleanup and removal of that dead code is still at least warranted. On Oct 18, 2016, at 9:15 AM, Oleksandr Petrov mailto:oleksandr.pet...@gmail.com>> wrote: Unit tests will be completel

8099 Storage Format Documentation as used with PRIMARY_INDEX

I'm working on writing Birch for trunk and I noticed the following: https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/columniterator/AbstractSSTableIterator.java#L503 Prior to 3.0 the offset was the literal offset into the data file, yet now we seem to be doing the

Re: Use of posix_fadvise

Within a single SegmentedFile? On Oct 18, 2016, at 9:02 AM, Ariel Weisberg mailto:ariel.weisb...@datastax.com>> wrote: With compaction there can be hot and cold data mixed together.

Re: Cleanup after yourselves please

commented tests. My branch is going > to be ready for review soon. > > [1] https://issues.apache.org/jira/browse/CASSANDRA-12373 > > > On Tue, Oct 18, 2016 at 5:10 PM Michael Kjellman < > mkjell...@internalcircle.com> wrote: > >> There was a bunch of tests has

Re: Use of posix_fadvise

ngs in the page cache that are no longer needed like compacted data that has been early opened elsewhere. On Oct 18, 2016 11:29 AM, "Michael Kjellman" mailto:mkjell...@internalcircle.com>> wrote: We use posix_fadvise in a bunch of places, and in stereotypical Cassandra fashion

Re: Use of posix_fadvise

ewhere. > > On Oct 18, 2016 11:29 AM, "Michael Kjellman" > wrote: > >> We use posix_fadvise in a bunch of places, and in stereotypical Cassandra >> fashion no comments were provided. >> >> There is a check the OS is Linux (okay, a start) but it turns

Re: Use of posix_fadvise

cid:543B66BF-5E99-4227-A24D-1AB8C0341D97@localhost] best, kjellman On Oct 18, 2016, at 8:33 AM, Benedict Elliott Smith mailto:bened...@apache.org>> wrote: ... and continuing in the fashion of behaviours one might like to disabuse people of, no code link is provided. On 18 October 201

Use of posix_fadvise

We use posix_fadvise in a bunch of places, and in stereotypical Cassandra fashion no comments were provided. There is a check the OS is Linux (okay, a start) but it turns out the behavior of providing a length of 0 to posix_fadvise changed in some 2.6 kernels. We don't check the kernel version

Cleanup after yourselves please

There was a bunch of tests hastily and messly commented out line by line (*whyy?*) ColumnFamilyStoreTest with comments that they are pending SuperColumns support post 8099. Could those responsible please cleanup after themselves? It's been a while since 8099 was committed in the first place an

Re: Question on assert

> IllegalStateException. Other times an class named "estimator" asserts when > the "estimate" "overflows". This seem far away from the defined purpose of > assert. > > The glaring issue is that it bubbles through try catch so it hardly makes > me fee

Re: Question on assert

ot; This is somewhat of my point. Why do assertions that sometimes are trapped "protect my data" better then a checked exception? On Wed, Sep 21, 2016 at 1:24 PM, Michael Kjellman < mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com>> wrote: I hate that commen

Re: Question on assert

I hate that comment with a passion. Please please please please do yourself a favor and *always* run with asserts on. `-ea` for life. In practice I'd be surprised if you actually got a reliable 5% performance win and I doubt your customers will care about a potential 5% performance win when you'

Re: Failing tests 2016-08-24 [cassandra-3.9]

Awesome Joel Sent from my iPhone On Aug 24, 2016, at 8:22 PM, Joel Knighton mailto:joel.knigh...@datastax.com>> wrote: === testall: All passed! === dtest: 2 failures scrub_test.TestScrubIndexes

Re: Failing tests 2016-08-22 [cassandra-3.9]

Looks like some very nice progress here! Mucho Exciting!! 💃🏻💃🏻💃🏻 On Aug 22, 2016, at 10:44 PM, Joel Knighton mailto:joel.knigh...@datastax.com>> wrote: === testall: All passed! === dtest: 2 failures

Thanks for all the fish.

Just wanted to say thank you publicly to Jonathan Ellis for his tireless work making this community and software what it is. He's always been level headed and I certainly wouldn't be where I am without his leadership. So, Jonathan, thanks for all the fish. best, kjellman Sent from my iPhone

Re: A proposal to move away from Jira-centric development

+1 Sent from my iPhone On Aug 15, 2016, at 6:48 PM, Brandon Williams mailto:dri...@gmail.com>> wrote: So will I, if that happens, which has never happened in the last ~7 years. On Mon, Aug 15, 2016 at 4:27 PM, Jeff Jirsa mailto:jeff.ji...@crowdstrike.com>> wrote: On 8/15/16, 2:15 PM, "Marvi

Re: A proposal to move away from Jira-centric development

aren’t the source of truth. They are. That’s not optional. If you are an ASF project, mailing lists are the source of truth. Period. On 8/15/16, 11:01 AM, "Michael Kjellman" mailto:mkjell...@internalcircle.com>> wrote: I'm a big fan of mailing lists, but google m

Re: A proposal to move away from Jira-centric development

I'm a big fan of mailing lists, but google makes issues very findable for new people to the project as JIRA gets indexed. They won't be able to find the same thing on an email they didn't get -- because they weren't in the project in the first place. Mailing lists are good for broad discussion

Re: Jira down, again?

Hm... weird, JIRA isn't working again? S bizarre!! 😂 > On Jun 15, 2016, at 5:38 PM, Michael Kjellman > wrote: > > down. again. > >> On Jun 14, 2016, at 11:14 AM, Alex Popescu wrote: >> >> I've been trying to get to a ticket for the la

Re: Jira down, again?

down. again. > On Jun 14, 2016, at 11:14 AM, Alex Popescu wrote: > > I've been trying to get to a ticket for the last 2h and I only get service > unavailable :-( > > On Tue, Jun 14, 2016 at 10:26 AM, Michael Kjellman < > mkjell...@internalcircle.com> w

Re: NewBie Question

This was forwarded to me yesterday... a helpful first step https://github.com/apache/cassandra/blob/cassandra-3.0.0/guide_8099.md > On Jun 15, 2016, at 9:54 AM, Jonathan Haddad wrote: > > Maybe some brave soul will document the 3.0 on disk format as part of > https://issues.apache.org/jira/brow

Re: Jira down, again?

have the same experience? >>> >>> Best Regards >>> >>> On Tue, Jun 14, 2016 at 4:19 AM, Brandon Williams >>> wrote: >>> >>>> Everyone. >>>> >>>> On Mon, Jun 13, 2016 at 3:18 PM, Michael Kjellman < >>>> mkjell...@internalcircle.com> wrote: >>>> >>>>> Seems like Apache Jira is 100% down, again, for like the 500th time in >>>> the >>>>> last 2 months. Just me or everyone? >

Jira down, again?

Seems like Apache Jira is 100% down, again, for like the 500th time in the last 2 months. Just me or everyone?

Re: NewBie Question ~ Book for Cassandra

Bhuvan, You didn't disrespect anyone, so please don't apologize! Appreciate your positive and helpful comment for the OP :) best, kjellman > On Jun 13, 2016, at 8:50 AM, Bhuvan Rawal wrote: > > Hi Matt, > > I suggested the resources keeping in mind the ease with which one can > learn. My id

Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

I the first person to ask that, and why didn’t a PMC member point that out right away and why did it take me asking to point to the Apache docs. This is what I am talking about in terms of the Apache community.. On 6/6/16, 4:47 PM, "Michael Kjellman" mailto:mkjell.

Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

http://cassandra.apache.org/doc/cql3/CQL.html On Jun 6, 2016, at 4:42 PM, Mattmann, Chris A (3980) mailto:chris.a.mattm...@jpl.nasa.gov>> wrote: Hi, So, the core documentation for a key part of Cassandra is hosted at DataStax? Cheers, Chris

Re: Cassandra Java Driver and DataStax

No need to argue your point to me anymore. I've already tuned you out. These are good people who I consider my friends and insulting people just shows your arguments really have no merit. Good luck with your new driver contribution! I look forward to reviewing the code. Sent from my iPhone

Re: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot

I'd recommend you create a JIRA! That way you can get some traction on the issue. Obviously an OOM is never correct, even if your process is wrong in some way! Best, kjellman Sent from my iPhone > On May 8, 2016, at 8:48 PM, Michael Fong > wrote: > > Hi, all, > > > Haven't heard any resp

Re: [Proposal] Mandatory comments

My vote is to start with BigTableScanner (SSTableScanner).. 5 iterators that all do something different with each other depending on how used with zero comments -- in a critical code path. What could go wrong! > On May 5, 2016, at 11:26 AM, Dave Brosius wrote: > > A less controversial tact wou

Re: Criteria for upgrading to 3.x releases in PROD

This is best for the users list. Test the releases yourself and then decide when it's ready for your use case, ops team, and organization. This is a personal decision and not one for *thousands* of others on this mailing list to make for you. best, kjellman > On Apr 18, 2016, at 10:54 AM, Anuj

Re: A short guid on how to contribute patches to Cassandra

Move to Wiki? Sent from my iPhone > On Feb 9, 2016, at 5:59 AM, Aleksey Yeschenko wrote: > > Hello everyone, > > I’ve compiled a short guide for contributors (who aren’t committers yet) > about how to properly contribute Cassandra patches: > > https://docs.google.com/document/d/1d_AzYQo74de9

Re: Versioning policy?

Correct, this is an open source project. If you want a Enterprise support story Datastax has an Enterprise option for you. > On Jan 16, 2016, at 11:19 AM, Anuj Wadehra wrote: > > Hi Jonathan > > It would be really nice if you could share your thoughts on the four points > raised regarding

Re: new version of Cassandra-stress doesn't support random read benchmark?

So #cassandra party in LA? Drinks on you? 😅 Sweet! Sent from my iPhone > On May 25, 2015, at 2:34 AM, graham sanderson wrote: > > Hey Benedict; > > I screwed up on email after a bachelor party, and sent something to external > cassandra-users not internal users (drunken drivel) > > I never s

Re: Proposal: release 2.2 (based on current trunk) before 3.0 (based on 8099)

Last I checked — and I could be wrong — we’ve never had to think about what to number a Cassandra version due to a ticket that could “impact” our users so dramatically due to the scope of the changes from a single ticket. Food for thought. love, kjellman > On May 11, 2015, at 2:20 PM, Alex Pop

Re: 3.0 and the Cassandra release process

For most of my life I’ve lived on the software bleeding edge both personally and professionally. Maybe it’s a personal weakness, but I guess I get a thrill out of the problem solving aspect? Recently I came to a bit of an epiphany — the closer I keep to the daily build — generally the happier I

  1   2   >