On 04 Apr 2014, at 11:18, prem yadav ipremya...@gmail.com wrote:
Though cassandra can work but to me it looks like you could use a persistent
queue for example (rabbitMQ) to implement this. All your workers can
subscribe to a queue.
In fact, why not just MySQL?
Hey, I have got a C*
Oh ok. I thought you did not have a cassandra cluster already. Sorry about
that.
On Fri, Apr 4, 2014 at 11:42 AM, Jan Algermissen jan.algermis...@nordsc.com
wrote:
On 04 Apr 2014, at 11:18, prem yadav ipremya...@gmail.com wrote:
Though cassandra can work but to me it looks like you could
@Jan
This subject of distributed workers queues has been discussed in the
mailing list many times. Basically one implementation can be:
1) *p* data providers, *c* data consumers
2) create partitions (physical rows) of arbitrary number of columns (let's
say 10 000, not too big though).
Hi DuyHai,
On 04 Apr 2014, at 13:58, DuyHai Doan doanduy...@gmail.com wrote:
@Jan
This subject of distributed workers queues has been discussed in the
mailing list many times.
Sorry + thanks.
Unfortunately, I do not want to use C* as a queue, but to coordinate workers
that page
You said you have tried the Pig URL split_size, but have you actually tried
decreasing the value of cassandra.input.split.size hadoop property? The
default is 65536, so you may want to decrease that to see if the number of
mappers increase. But at some point, even if you lower that value it will
http://www.datastax.com/documentation/developer/java-driver/2.0/java-driver/tracing_t.html
On Fri, Apr 4, 2014 at 11:34 AM, Apoorva Gaurav
apoorva.gau...@myntra.comwrote:
On Fri, Apr 4, 2014 at 9:37 PM, Tyler Hobbs ty...@datastax.com wrote:
On Fri, Apr 4, 2014 at 12:41 AM, Apoorva Gaurav
Hi All,
We would like to secure our Cassandra database. We don't want anybody to
read/write on our Cassandra database leaving our team members only.
We are using Cassandra 1.2.9 in Production and we have 36 node Cassandra
cluster. 12 in each colo as we have three datacenters.
But we would
