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
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
On Sat, Jul 16, 2011 at 12:30 PM, Jeremy Hanna
jeremy.hanna1...@gmail.com 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
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 dri...@gmail.com wrote:
You should mark it 'patch available' so someone will know to review it.
On
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 jbel...@gmail.com wrote:
I think the in progress status is preventing Patch Available somehow?
In any case, I've asked Pavel to review. Thanks for
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 jbel...@gmail.com wrote:
I think the in progress status is preventing Patch
