MX4J support broken in cassandra 3.0.5?

Hi guys, I'm upgrading from cassandra 2.1 to cassandra 3.0.5 and mx4j support seems to be broker. An empty html page is shown: > GET / HTTP/1.1 > Host: localhost:8081 > User-Agent: curl/7.43.0 > Accept: */* > * HTTP 1.0, assume close after body < HTTP/1.0 200 OK < expires: now < Server:

WARN Writing large partition for materialized views

in the schema design. Thanks, Robert Sicoie

How to get rid of "Cannot start multiple repair sessions over the same sstables" exception

Hi guys, I have a cluster of 5 nodes, cassandra 3.0.5. I was running nodetool repair last days, one node at a time, when I first encountered this exception *ERROR [ValidationExecutor:11] 2016-09-27 16:12:20,409 CassandraDaemon.java:195 - Exception in thread Thread[ValidationExecutor:11,1,main]*

Re: How to get rid of "Cannot start multiple repair sessions over the same sstables" exception

Thanks Alexander, After roll restart the blocked repair job stopped and I was able to run repair again. Regards, Robert Robert Sicoie On Wed, Sep 28, 2016 at 6:46 PM, Alexander Dejanovski < a...@thelastpickle.com> wrote: > Robert, > > You can restart them in any order, th

Re: WARN Writing large partition for materialized views

Thanks! Robert Sicoie On Thu, Sep 29, 2016 at 12:49 PM, Alexander Dejanovski < a...@thelastpickle.com> wrote: > Hi Robert, > > Materialized Views are regular C* tables underneath, so based on their PK > they can generate big partitions. > It is often advised to keep parti

Re: How to get rid of "Cannot start multiple repair sessions over the same sstables" exception

, Robert Robert Sicoie On Wed, Sep 28, 2016 at 5:35 PM, Alexander Dejanovski < a...@thelastpickle.com> wrote: > They will show up in nodetool compactionstats : https://issues.apache.org/ > jira/browse/CASSANDRA-9098 > > Did you check nodetool tpstats to see if you didn't have an

Property file snitch and unbalanced cluster

Hi guys, I have a cluster with 5 nodes, cassandra 3.0.5, RF=2, PropertyFileSnitch. Three of the nodes were added initially, DC=PRD. The other two were added more recently. The default for unknown nodes default=DC1:r1 (which is bad in my case, as it would have been nice to have PRD as default)

Re: Exception thrown on repair after change was made to existing cassandra type

Thank you Alexander, The restart did the trick. Thank you, Robert Robert Sicoie On Tue, Dec 6, 2016 at 5:00 PM, Alexander Dejanovski <a...@thelastpickle.com > wrote: > Hi Robert, > > Some of your nodes did not accept the new schema, or several alter > commands were issued

Exception thrown on repair after change was made to existing cassandra type

Hi guys, I am running cassandra 3.0.5 on 5 nodes, NetworkTopologyStrategy, factor 2 I had to add new 3 columns to an existing type and I've done it through cqlsh. After one of the alter commands I've got *OperationTimedOut: errors={'x.x.x.x': 'Request timed out while waiting for schema

Re: Exception thrown on repair after change was made to existing cassandra type

Any suggestion is more than welcome. The fact is that the same alter commands worked in two other environments and now fails in the thirds environment. No downtime is accepted. Thanks, Robert Robert Sicoie On Tue, Dec 6, 2016 at 4:11 PM, Robert Sicoie <robert.sic...@gmail.com> wrote: >

Streaming error during repair

Hi guys, While running repairs, I see this on one box: *ERROR [RepairJobTask:19] 2017-01-05 09:12:36,940 RepairSession.java:290 - [repair #3747c581-d325-11e6-92ea-130d59760dad] Session completed with the following error* *org.apache.cassandra.exceptions.RepairException: [repair

Re: Streaming error during repair

Yes, I am running repairs in one single command. Thanks Paulo! Robert Sicoie On Thu, Jan 5, 2017 at 1:59 PM, Paulo Motta <pauloricard...@gmail.com> wrote: > Fixed on https://issues.apache.org/jira/browse/CASSANDRA-12905 (still to > be released). If you're running repair of