browse/JAVA-603
> which seem to match the Cassandra/DataStax community version but not the
> driver version.
>
> On Mon, Mar 21, 2016 at 9:33 PM, Thunder Stumpges <
> thunder.stump...@gmail.com> wrote:
>
>> Hi guys,
>>
>> So, quick background, we are using O
Hi guys,
So, quick background, we are using Outworkers (previously WebSudos) Phantom
v 1.22.0 Which appears to be using DataStax driver 3.0.0. We are running
scala 2.10 inside Samza on Yarn (CDH 5.4.4) with Oracle JDK 8.
This is all pointing at a 3 node dev cluster of DataStax Community v 2.1.13
Hi guys,
We have recently added two datacenters to our existing 2.0.6 cluster. We
followed the process here pretty much exactly:
http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_add_dc_to_cluster_t.html
We are using GossipingPropertyFileSnitch and NetworkTopologyStrategy across
med addressee and may be
>> confidential. If you are not the intended recipient, you are reminded that
>> the information remains the property of the sender. You must not use,
>> disclose, distribute, copy, print or rely on this e-mail. If you have
>> received this message in
Would it help here to not actually issue a delete statement but instead use
date based compaction and a dynamically calculated ttl that is some safe
distance in the future from your key?
Just a thought.
-Thunder
On Mar 25, 2015 11:07 AM, "Robert Coli" wrote:
> On Wed, Mar 25, 2015 at 12:45 AM,
Hi all,
I am looking into an issue we ran into last night with a single node in our
three node 2.0.6 cluster. The top level symptoms were timed out writes, and
high latency read and write.
Looking into it more, the node experienced all of these during this two
hour window which it eventually reco
This seems a bit overkill. We run far more than 100mps (closer to 600) in
rabbit with very good latency on a 3 node cluster. It has been very reliable as
well.
Thunder
- Reply message -
From: "Jagan Ranganathan"
To:
Subject: Queuing System
Date: Sat, Feb 22, 2014 9:06 AM
Thanks Tupsh
We use this same setup also and it works great.
Thunder
- Reply message -
From: "Laing, Michael"
To:
Subject: Queuing System
Date: Sat, Feb 22, 2014 7:31 AM
We use RabbitMQ for queuing and Cassandra for persistence.
RabbitMQ with clustering and/or federation should meet your high avail
If you are looking for write throughput and running on a VM you could likely
have IO issues with your virtual disks.. Best practices are to put the write
ahead log on a separate disk from the data folder(s). Not sure if you have done
this or what physical setup you have under the VM but I would
ads result in reliable data? My understanding is it should have always
hit one of the other two nodes in addition to itself, and resulted in
consistent data...?
thanks,
Thunder
On Thu, Feb 6, 2014 at 2:04 PM, Thunder Stumpges wrote:
> I guess so, it likely was listed in the seeds in cassandr
2014 4:23 PM, Thunder Stumpges
> wrote:
> Hi all,
>
> We recently needed/wanted to reconfigure the disks for our 3-node
> C*2.0.4 Cassandra setup and rebuild the server at the same time. Upon
> adding the newly rebuilt server into the cluster, it immediately started
> serving
Hi all,
We recently needed/wanted to reconfigure the disks for our 3-node C*2.0.4
Cassandra setup and rebuild the server at the same time. Upon adding the
newly rebuilt server into the cluster, it immediately started serving read
requests with no data! Then because the latency is so "good" the vas
-CDH4
regards,
Thunder
On Tue, Feb 4, 2014 at 1:40 PM, Cyril Scetbon wrote:
> Hi,
>
> Look for posts from Thunder Stumpges in this mailing list. I know he has
> succeeded to make it Hadoop 2.x work with Cassandra 2.x
>
> For those who are interested in using it with Cassandra
mn family for this in cassandra..if i
>> design as is then for search of India, Pen then i will select India, Pen
>> columns but that will touch each and every row because i am not able to
>> apply criteria of matching 1s only...i believe there can be better design
>> of t
Hey Naresh,
You asked a similar question a week or two ago. It looks like you have
simplified your needs quite a bit. Were you able to adjust your
requirements or separate the issue? You had a complicated time dimension
before, as well as a single "query" for multiple AND cases on tags.
> c)
Well, I haven't tried it, but that IS kinda the point of Enterprise vs
Community/free. We have the community version and all of the enterprise
features basically say "sorry you need enterprise version to use this feature"
..
Perhaps if you are evaluating whether you want to spend the money on a
I'm not sure if this is your issue as I have not used these triggers before but
shouldn't the invertedindex table have a different primary key than the primary
table (either f2 or f3)?
-Thunder
> On Jan 11, 2014, at 12:03 PM, Vidit Asthana wrote:
>
> I am new to cassandra and trying to run t
alternative to cassandra, i tried Apache Blur, in blur table i am
>>>> able to store exact same data and all queries also worked..so blur allows
>>>> dynamic indexing of tag column BUT moving away from cassandra, i am
>>>> loosing its strength beca
I don't have specific experience upgrading from 1.x to 2.x but I do have to
say that if you have Pig/Hadoop integration working, go with that. I ran
into many small issues getting the integration working with just the right
version of Hadoop/Pig/and Cassandra 2.0.x
On Jan 9, 2014, at 8:46 AM, Mig
Well I think you have essentially time-series data, which C* should handle
well, however I think your "Tag" column is going to cause troubles. C* does
have collection columns, but they are not indexable nor usable in WHERE
clause. Your example has both the uniqueness of the data (primary key) and
q
This sort of work sounds much more like a Hadoop/Hive/Pig type of analysis.
What are your latency requirements on queries? Are they ad-hoc or part of an
application? What is the case where you would need to change an existing value?
If it is write once, then Hadoop/Hive is great, if it changes
1 collections, 7276089816used;
>>> max is 8375238656
>>> INFO [ScheduledTasks:1] 2014-01-02 12:33:08,557 GCInspector.java (line
>>> 116) GC for ConcurrentMarkSweep: 554 ms for 1 collections, 7662839184 used;
>>> max is 8375238656
>>>
>>> The earliest
ayed requests is 12:32:00.083 and
>> they all clear out at 12:32:00.517. GC log events occur at 12:31:50 and at
>> 21:32:06. The above entries are the only log entries in system.log at this
>> time. Any other ideas?
>>
>> Is this type of GC frequency and delay "nor
GC frequency and delay "normal" ?
thanks,
Thunder
On Thu, Jan 2, 2014 at 2:27 PM, Robert Coli wrote:
> On Thu, Jan 2, 2014 at 2:24 PM, Thunder Stumpges <
> thunder.stump...@gmail.com> wrote:
>
>> Excuse my ignorance, but where would I look for the GC info? Wh
ventbrite.com/what-version-of-cassandra-should-i-run/
>
>
> =Rob
>
>
> On Thu, Jan 2, 2014 at 2:13 PM, Robert Coli wrote:
>
>> On Thu, Jan 2, 2014 at 2:05 PM, Thunder Stumpges <
>> thunder.stump...@gmail.com> wrote:
>>
>>> I am seeing a rea
Hi all,
I am seeing a read operation delay in our small (3 node) cluster where I am
testing. The "normal" latency for these operations is < 2ms as recorded by
our load client. This holds easily beyond several hundred qps. However
there are times when all incoming queries (on a node-by-node basis)
26 matches
Mail list logo
