Hi Tim,
In case the above doesn't work, another thing to be aware of is that JMX
uses 2 different ports. The initial connection to 7199 causes a second port
to be opened, which is normally assigned randomly to an available and
otherwise unused port above 1024. If your server has a
:
Thank you all for your advice and good info. The node has died a
couple of times with out of memory errors. I've restarted each time but it
starts re - running compaction and then dies again.
Is there a better way to do this?
On Apr 18, 2014 6:06 PM, Steven A Robenalt srobe...@stanford.edu
wrote
There's a little-known change in the way JMX uses ports that was add to
JDK7u4 which simplifies the use of JMX in a firewalled environment.
The standard RMI registry port for JMX is controlled by the
com.sun.management.jmxremote.port property. The change to Java 7 was to
introduce the related
Is there a reason you can't use:
DELETE FROM table_name WHERE s = ? AND p = ? AND o = ? AND c = ?;
On Mon, Apr 21, 2014 at 6:51 PM, Eric Plowe eric.pl...@gmail.com wrote:
Also I don't think you can null out columns that are part of the primary
key after they've been set.
On Monday, April
Looking back through this email chain, it looks like Phil said he wasn't
using vnodes.
For the record, we are using vnodes since we brought up our first cluster,
and have not seen any issues with bootstrapping new nodes either to replace
existing nodes, or to grow/shrink the cluster. We did
Hi Kasper,
I'd suggest taking a look at Spark, Storm, or Samza (all are Apache
projects) for a possible approach. Depending on your needs and your
existing infrastructure, one of those may work better than others for you.
Steve
On Tue, Apr 1, 2014 at 2:51 AM, Kasper Petersen
Okay, I'm officially lost on this thread. If you plan on forking Cassandra
to preserve and continue to enhance the Thrift interface, you would also
want to add a bunch of relational features to CQL as part of that same fork?
On Tue, Mar 11, 2014 at 6:20 PM, Edward Capriolo
I should add that I'm not trying to ignite a flame war. Just trying to
understand your intentions.
On Tue, Mar 11, 2014 at 6:50 PM, Steven A Robenalt srobe...@stanford.eduwrote:
Okay, I'm officially lost on this thread. If you plan on forking Cassandra
to preserve and continue to enhance
, 2014 at 1:30 AM, Steven A Robenalt
srobe...@stanford.eduwrote:
Hi Kasper,
I am assuming that your friend list is symmetric (i.e. If I am your
friend then you are also my friend), which your comments seem to indicate.
First, I would suggest that you drop the friends score as a part
Hi Kasper,
I am assuming that your friend list is symmetric (i.e. If I am your friend
then you are also my friend), which your comments seem to indicate.
First, I would suggest that you drop the friends score as a part of the
clustering key, which eliminates the need to read-before-write.
With
Hi Jacob,
I get the same effect using:
update mytable set count = count + 0 where day = 20140103
The count field is changed from null to zero as a result.
Steve
On Wed, Feb 12, 2014 at 6:31 PM, Jacob Rhoden jacob.rho...@me.com wrote:
Hi Guys,
My question is probably best described by
I am as well.
Thanks,
Steve
On Thu, Feb 6, 2014 at 4:13 PM, Alex Popescu al...@datastax.com wrote:
On Thu, Feb 6, 2014 at 3:50 PM, Clint Kelly clint.ke...@gmail.com wrote:
I can
post a link if anyone is curious (once it is done).
I'm curious... thanks
--
:- a)
@al3xandru
Hi Chap,
You don't indicate which version of Cassandra and what client side driver
you are using, but I have seen the same behavior with Cassandra 2.0.2 and
earlier versions of the Java Driver. With Cassandra 2.0.3 and the 2.0.0rc2
driver, my read timeouts are basically nonexistent at my current
of those
timeouts under earlier 2.x versions and really hoped they were the source
of our problem but unfortunately that doesn't seem to be the case.
Thanks again,
Chap
On 5 Feb 2014, at 17:49, Steven A Robenalt wrote:
Hi Chap,
You don't indicate which version of Cassandra and what client
Hi Chiru,
I would recommend that you consider building your Java application around
CQL3 and the Datastax Java Driver instead. While a JDBC driver gives a
familiar interface, it doesn't give you access to the full power of
Cassandra. If you really want to use JDBC, you may be better off with an
://github.com/datastax/java-driver) source and created jar ,but no
luck.
Where can we found pre compiled Jar which is suitable for Apache
Cassandra 2.0.4 version.
Regards,
Chiru
On 25-Jan-2014, at 1:15 AM, Steven A Robenalt srobe...@stanford.edu
wrote:
be
--
Steve Robenalt
Software Architect
My understanding is that it's generally a Cassandra anti-pattern to do
read-before-write in any case, not just because of this issue. I'd agree
with Robert's suggestion earlier in this thread of writing each update
independently and aggregating on read.
Steve
On Fri, Jan 10, 2014 at 2:35 PM,
repeated writing is not an issue. Why would this be bad?
Robert
*From: *Steven A Robenalt srobe...@stanford.edu
*Reply-To: *user@cassandra.apache.org
*Date: *Friday, January 10, 2014 at 3:41 PM
*To: *user@cassandra.apache.org
*Subject: *Re: Read/Write consistency issue
My understanding
easily be worked around, IMO. It would just require a bit of housekeeping
to keep track of your counters and lazily delete them.
But yes, I third Robert's suggestion of aggregate on read instead of
write.
-Tupshin
On Fri, Jan 10, 2014 at 5:41 PM, Steven A Robenalt srobe...@stanford.edu
,
One question, which is confusing , it's a server side issue or client side?
-Vivek
On Tue, Dec 24, 2013 at 12:30 PM, Vivek Mishra mishra.v...@gmail.comwrote:
Hi Steven,
Thanks for your reply. We are using version 1.2.9.
-Vivek
On Tue, Dec 24, 2013 at 12:27 PM, Steven A Robenalt
Hi Vivek,
Which release are you using? We had an issue with 2.0.2 that was solved by
a fix in 2.0.3.
On Mon, Dec 23, 2013 at 10:47 PM, Vivek Mishra mishra.v...@gmail.comwrote:
Also to add. It works absolutely fine on single node.
-Vivek
On Tue, Dec 24, 2013 at 12:15 PM, Vivek Mishra
/CASSANDRA-6299
I built and deployed a 2.0.3 snapshot this morning, which includes this
fix, and my cluster is now behaving normally (no read timeouts so far).
On Tue, Nov 19, 2013 at 4:55 PM, Steven A Robenalt srobe...@stanford.eduwrote:
It seems that with NTP properly configured, the replication
Thanks Michael, I will try that out.
On Tue, Nov 19, 2013 at 5:28 AM, Laing, Michael
michael.la...@nytimes.comwrote:
We had a similar problem when our nodes could not sync using ntp due to
VPC ACL settings. -ml
On Mon, Nov 18, 2013 at 8:49 PM, Steven A Robenalt
srobe...@stanford.eduwrote
It seems that with NTP properly configured, the replication is now working
as expected, but there are still a lot of read timeouts. The
troubleshooting continues...
On Tue, Nov 19, 2013 at 8:53 AM, Steven A Robenalt srobe...@stanford.eduwrote:
Thanks Michael, I will try that out.
On Tue
Hi all,
I am attempting to bring up our new app on a 3-node cluster and am having
problems with frequent read timeouts and slow inter-node replication.
Initially, these errors were mostly occurring in our app server, affecting
0.02%-1.0% of our queries in an otherwise unloaded cluster. No
25 matches
Mail list logo
