Announcements List
What do we think about having a separate mailing list for just cassandra related announcements. The main purpose being announcing new releases once they pass a vote and are put up on the website. I think there is a desire for a way to be informed when new releases are available without sifting through the dev or users mailing lists.
Re: Announcements List
I think this is a good idea. It would be helpful for a lot of people who don't want to monitor dev, but they want the artifacts that come out of it. On 7/18/11 7:26 AM, Nick Bailey wrote: What do we think about having a separate mailing list for just cassandra related announcements. The main purpose being announcing new releases once they pass a vote and are put up on the website. I think there is a desire for a way to be informed when new releases are available without sifting through the dev or users mailing lists. -- Ben Coverston Director of Operations DataStax -- The Apache Cassandra Company http://www.datastax.com/
Re: Announcements List
Following @cassandra on twitter or a google alert would be simple enough I think. Gary. On Mon, Jul 18, 2011 at 14:26, Nick Bailey wrote: > What do we think about having a separate mailing list for just > cassandra related announcements. The main purpose being announcing new > releases once they pass a vote and are put up on the website. I think > there is a desire for a way to be informed when new releases are > available without sifting through the dev or users mailing lists. >
Read asynchronously from multiple nodes
I am developing a new API call which will read results from multiple nodes. I am first sending a message to each node and maintain a list of handlers, one for each message. However, after all requests are sent, I can only call the handlers' get() function sequentially, wait for each to finish and then call the next one. This causes unnecessary delay: if the second node has already computed and sent a response, but the first one hasn't, the first handler's get() is blocking until the first node has finished, before advancing to the second node. Ideally, I would like to receive the output of the first node to finish, as soon as it is finished. I have read about the SEDA design, and I think a solution would be to submit a callable for each node to the READ stage, while gathering the results in a (synchronized) Vector. However, I can't figure out how to do that and whether it will work as I am describing. This might also be beneficial for getRangeSlice(), which, as far as I understand, gets all results from one node before advancing to the next. For particularly large range queries, it might be better to just send the message to two nodes at once: if the next node responds with an empty list, the coordinator knows it isn't necessary to send the request to further nodes. In conclusion, please explain how to submit to the READ stage, and comment on getRangeSlice(). Alexander
Re: Announcements List
I think a lot of people follow cassandra on twitter. However I don't think it would be a big deal to email both user@ and announcements@ when a new release is out, if people don't mind the extra list. Nick - is this from people asking about this? On Jul 18, 2011, at 9:50 AM, Gary Dusbabek wrote: > Following @cassandra on twitter or a google alert would be simple enough I > think. > > Gary. > > On Mon, Jul 18, 2011 at 14:26, Nick Bailey wrote: > >> What do we think about having a separate mailing list for just >> cassandra related announcements. The main purpose being announcing new >> releases once they pass a vote and are put up on the website. I think >> there is a desire for a way to be informed when new releases are >> available without sifting through the dev or users mailing lists. >>
Re: Announcements List
I have mixed feeling about that. On the one side, I agree with Gary that it doesn't add any real value. There is twitter, and we use consistent tagged subjects for release email, so it's easy to subscribe to the user list and set up a filter. That being said, I could understand that some people may find it cleaner to have a separate announce list and it is not something unheard of, so I'm ok with that if enough people thinks it's a good idea. But I think there is at least 2 questions that come along: - should it be moderated ? - should announces still be sent to the user list ? -- Sylvain On Mon, Jul 18, 2011 at 4:50 PM, Gary Dusbabek wrote: > Following @cassandra on twitter or a google alert would be simple enough I > think. > > Gary. > > On Mon, Jul 18, 2011 at 14:26, Nick Bailey wrote: > >> What do we think about having a separate mailing list for just >> cassandra related announcements. The main purpose being announcing new >> releases once they pass a vote and are put up on the website. I think >> there is a desire for a way to be informed when new releases are >> available without sifting through the dev or users mailing lists. >> >
Re: Announcements List
On Mon, Jul 18, 2011 at 10:32 AM, Sylvain Lebresne wrote: > That being said, I could understand that some people may find it > cleaner to have a > separate announce list and it is not something unheard of, so I'm ok > with that if enough > people thinks it's a good idea. Ditto. > - should it be moderated ? Yes. > - should announces still be sent to the user list ? Yes. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: Announcements List
DataStax has had requests for something like this. It seems like something that would be generally useful for the community though. Regarding twitter, I'm not sure a twitter account should be required to get that information. I think you can follow a twitter account as an rss feed though, so that might be a solution. That and the google alert or email filter solutions just seem to be introducing more difficulty for anyone trying to get that information. Perhaps the demand for this isn't as high as I am imagining though. My opinion on the list if we decide to go with that is that only committers would be able to post to it and yes it would go to the users list as well. On Mon, Jul 18, 2011 at 10:32 AM, Sylvain Lebresne wrote: > I have mixed feeling about that. > > On the one side, I agree with Gary that it doesn't add any real value. > There is twitter, > and we use consistent tagged subjects for release email, so it's easy > to subscribe > to the user list and set up a filter. > > That being said, I could understand that some people may find it > cleaner to have a > separate announce list and it is not something unheard of, so I'm ok > with that if enough > people thinks it's a good idea. But I think there is at least 2 > questions that come along: > - should it be moderated ? > - should announces still be sent to the user list ? > > -- > Sylvain > > On Mon, Jul 18, 2011 at 4:50 PM, Gary Dusbabek wrote: >> Following @cassandra on twitter or a google alert would be simple enough I >> think. >> >> Gary. >> >> On Mon, Jul 18, 2011 at 14:26, Nick Bailey wrote: >> >>> What do we think about having a separate mailing list for just >>> cassandra related announcements. The main purpose being announcing new >>> releases once they pass a vote and are put up on the website. I think >>> there is a desire for a way to be informed when new releases are >>> available without sifting through the dev or users mailing lists. >>> >> >
Re: set rpc_timeout_in_ms via jmx?
On Sat, Jul 16, 2011 at 12:30 PM, Jeremy Hanna wrote: > I don't see a way in DatabaseDescriptor to set the rpc_timeout_in_ms via jmx. > > It doesn't seem possible right now. > > Is there any reason why that couldn't be set via jmx? It seems like a > rolling restart to update that is pretty heavy. It would be nice to set it > in the yaml and set it via jmx so it wouldn't require restart to take effect > immediately. > > Jeremy > > btw I'm trying to do that with my analytics nodes - hadoop jobs fail when > cycling a single cassandra node - might be 2388 I guess. There's no way to do this currently, but we'd be interested in having it. Ideally, the timeout would be configurable per request so that mixed workloads can have different timeouts. -ryan
Re: Tickets for someone looking to get his or her feet wet in Cassandra internals
I attached a patch to CASSANDRA-2717 a week or so ago. Should I be doing anything else to make sure it gets reviewed? Jim On Tue, Jul 5, 2011 at 11:31 AM, Jonathan Ellis wrote: > I regularly get requests for pointers to "starter" tickets. I suggest > we tag such tickets as LHF (for low-hanging fruit). I've tagged four > such to get started: > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12310865+AND+labels+%3D+lhf > > I'll try to keep this up to date. > > Aspiring contributors should also see > http://wiki.apache.org/cassandra/HowToContribute, and feel free to > drop by #cassandra-dev on freenode. > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
Re: Tickets for someone looking to get his or her feet wet in Cassandra internals
You should mark it 'patch available' so someone will know to review it. On Mon, Jul 18, 2011 at 2:55 PM, Jim Ancona wrote: > I attached a patch to CASSANDRA-2717 a week or so ago. Should I be > doing anything else to make sure it gets reviewed? > > Jim > > On Tue, Jul 5, 2011 at 11:31 AM, Jonathan Ellis wrote: >> I regularly get requests for pointers to "starter" tickets. I suggest >> we tag such tickets as LHF (for low-hanging fruit). I've tagged four >> such to get started: >> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12310865+AND+labels+%3D+lhf >> >> I'll try to keep this up to date. >> >> Aspiring contributors should also see >> http://wiki.apache.org/cassandra/HowToContribute, and feel free to >> drop by #cassandra-dev on freenode. >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of DataStax, the source for professional Cassandra support >> http://www.datastax.com >> >
Re: Tickets for someone looking to get his or her feet wet in Cassandra internals
I think the "in progress" status is preventing Patch Available somehow? In any case, I've asked Pavel to review. Thanks for following up, Jim. On Mon, Jul 18, 2011 at 2:57 PM, Brandon Williams wrote: > You should mark it 'patch available' so someone will know to review it. > > On Mon, Jul 18, 2011 at 2:55 PM, Jim Ancona wrote: >> I attached a patch to CASSANDRA-2717 a week or so ago. Should I be >> doing anything else to make sure it gets reviewed? >> >> Jim >> >> On Tue, Jul 5, 2011 at 11:31 AM, Jonathan Ellis wrote: >>> I regularly get requests for pointers to "starter" tickets. I suggest >>> we tag such tickets as LHF (for low-hanging fruit). I've tagged four >>> such to get started: >>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12310865+AND+labels+%3D+lhf >>> >>> I'll try to keep this up to date. >>> >>> Aspiring contributors should also see >>> http://wiki.apache.org/cassandra/HowToContribute, and feel free to >>> drop by #cassandra-dev on freenode. >>> >>> -- >>> Jonathan Ellis >>> Project Chair, Apache Cassandra >>> co-founder of DataStax, the source for professional Cassandra support >>> http://www.datastax.com >>> >> > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: Tickets for someone looking to get his or her feet wet in Cassandra internals
I had to reassign it myself to mark it patch available, then assign back to Jim. Stupid jira. On Mon, Jul 18, 2011 at 3:03 PM, Jonathan Ellis wrote: > I think the "in progress" status is preventing Patch Available somehow? > > In any case, I've asked Pavel to review. Thanks for following up, Jim. > > On Mon, Jul 18, 2011 at 2:57 PM, Brandon Williams wrote: >> You should mark it 'patch available' so someone will know to review it. >> >> On Mon, Jul 18, 2011 at 2:55 PM, Jim Ancona wrote: >>> I attached a patch to CASSANDRA-2717 a week or so ago. Should I be >>> doing anything else to make sure it gets reviewed? >>> >>> Jim >>> >>> On Tue, Jul 5, 2011 at 11:31 AM, Jonathan Ellis wrote: I regularly get requests for pointers to "starter" tickets. I suggest we tag such tickets as LHF (for low-hanging fruit). I've tagged four such to get started: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12310865+AND+labels+%3D+lhf I'll try to keep this up to date. Aspiring contributors should also see http://wiki.apache.org/cassandra/HowToContribute, and feel free to drop by #cassandra-dev on freenode. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com >>> >> > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
Re: Tickets for someone looking to get his or her feet wet in Cassandra internals
Thanks for the quick response! So the correct procedure is to attach the patch and make sure the issue is in "Patch Available" status? I'll try to do that next time. Jim On Mon, Jul 18, 2011 at 4:03 PM, Jonathan Ellis wrote: > I think the "in progress" status is preventing Patch Available somehow? > > In any case, I've asked Pavel to review. Thanks for following up, Jim. > > On Mon, Jul 18, 2011 at 2:57 PM, Brandon Williams wrote: >> You should mark it 'patch available' so someone will know to review it. >> >> On Mon, Jul 18, 2011 at 2:55 PM, Jim Ancona wrote: >>> I attached a patch to CASSANDRA-2717 a week or so ago. Should I be >>> doing anything else to make sure it gets reviewed? >>> >>> Jim >>> >>> On Tue, Jul 5, 2011 at 11:31 AM, Jonathan Ellis wrote: I regularly get requests for pointers to "starter" tickets. I suggest we tag such tickets as LHF (for low-hanging fruit). I've tagged four such to get started: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12310865+AND+labels+%3D+lhf I'll try to keep this up to date. Aspiring contributors should also see http://wiki.apache.org/cassandra/HowToContribute, and feel free to drop by #cassandra-dev on freenode. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com >>> >> > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
Re: Tickets for someone looking to get his or her feet wet in Cassandra internals
Right, that's what we typically use as a "needs review" dashboard. On Mon, Jul 18, 2011 at 3:08 PM, Jim Ancona wrote: > Thanks for the quick response! So the correct procedure is to attach > the patch and make sure the issue is in "Patch Available" status? > > I'll try to do that next time. > > Jim > > On Mon, Jul 18, 2011 at 4:03 PM, Jonathan Ellis wrote: >> I think the "in progress" status is preventing Patch Available somehow? >> >> In any case, I've asked Pavel to review. Thanks for following up, Jim. >> >> On Mon, Jul 18, 2011 at 2:57 PM, Brandon Williams wrote: >>> You should mark it 'patch available' so someone will know to review it. >>> >>> On Mon, Jul 18, 2011 at 2:55 PM, Jim Ancona wrote: I attached a patch to CASSANDRA-2717 a week or so ago. Should I be doing anything else to make sure it gets reviewed? Jim On Tue, Jul 5, 2011 at 11:31 AM, Jonathan Ellis wrote: > I regularly get requests for pointers to "starter" tickets. I suggest > we tag such tickets as LHF (for low-hanging fruit). I've tagged four > such to get started: > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12310865+AND+labels+%3D+lhf > > I'll try to keep this up to date. > > Aspiring contributors should also see > http://wiki.apache.org/cassandra/HowToContribute, and feel free to > drop by #cassandra-dev on freenode. > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com > >>> >> >> >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of DataStax, the source for professional Cassandra support >> http://www.datastax.com >> > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
