Re: Cassandra 2.1 on Xenial

[Michael Shuler]

Yep. This was fixed for 2.1.15, 2.2.7, 3.0.6, 3.6 in
https://issues.apache.org/jira/browse/CASSANDRA-10853

-- 
Kind regards,
Michael

On 03/18/2018 10:55 PM, Cyril Scetbon wrote:
> Okay I found that when building the package, the new helper dh_python2
> must be used to fix that issue.
> 
> —
> Cyril Scetbon
> 
>> On Mar 18, 2018, at 11:08 AM, Cyril Scetbon > > wrote:
>>
>> Hey guys,
>>
>> Having to still use Cassandra 2.1, I have installed it on Ubuntu
>> Xenial and I have an issue with cqlsh. I was able to fix it by
>> installing python-support and a fix from 2.1.16. However I’d like to
>> know if there is a way to do it without installing an old package
>> (python-support) on Xenial. dh-python is supposed to have replaced
>> python-support, however cqlsh complains when it’s not installed : 
>>
>> Traceback (most recent call last):
>>   File "/usr/bin/cqlsh", line 121, in 
>>     from cqlshlib import cql3handling, cqlhandling, pylexotron,
>> sslhandling
>> ImportError: No module named cqlshlib
>>
>> Is there a better way than installing that old package ?
>>
>> Thanks 
>> —
>> Cyril Scetbon
>>
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra 2.1 on Xenial

[Michael Shuler]

dh_python is a build dependency. The runtime dependency is python.

https://github.com/apache/cassandra/blob/cassandra-2.1/debian/control#L6
https://github.com/apache/cassandra/blob/cassandra-2.1/debian/control#L14

Just upgrading to the latest 2.1.x should fix all these issues your
having. :)

Michael

On 03/22/2018 09:59 PM, Cyril Scetbon wrote:
> Yeah, I also had to grab a new version of the cassandra-driver which was
> fixed in 2.1.16 https://issues.apache.org/jira/browse/CASSANDRA-11850
> otherwise cqlsh would not work with python 2.7.12.
> 
> I’m surprised dh-python is not a requirement on the Cassandra package in
> your debian/control 😮
> 
> I also noticed that I get issues with cassandra-stress on
> Xenial https://pastebin.com/raw/r2umZXSV, Any idea ? 
> 
> Bests
> —
> Cyril Scetbon
> 
>> On Mar 19, 2018, at 12:16 PM, Michael Shuler > <mailto:mich...@pbandjelly.org>> wrote:
>>
>> Yep. This was fixed for 2.1.15, 2.2.7, 3.0.6, 3.6 in
>> https://issues.apache.org/jira/browse/CASSANDRA-10853
>>
>> -- 
>> Kind regards,
>> Michael
>>
>> On 03/18/2018 10:55 PM, Cyril Scetbon wrote:
>>> Okay I found that when building the package, the new helper dh_python2
>>> must be used to fix that issue.
>>>
>>> —
>>> Cyril Scetbon
>>>
>>>> On Mar 18, 2018, at 11:08 AM, Cyril Scetbon >>> <mailto:cyril.scet...@free.fr>
>>>> <mailto:cyril.scet...@free.fr>> wrote:
>>>>
>>>> Hey guys,
>>>>
>>>> Having to still use Cassandra 2.1, I have installed it on Ubuntu
>>>> Xenial and I have an issue with cqlsh. I was able to fix it by
>>>> installing python-support and a fix from 2.1.16. However I’d like to
>>>> know if there is a way to do it without installing an old package
>>>> (python-support) on Xenial. dh-python is supposed to have replaced
>>>> python-support, however cqlsh complains when it’s not installed : 
>>>>
>>>> Traceback (most recent call last):
>>>>   File "/usr/bin/cqlsh", line 121, in 
>>>>     from cqlshlib import cql3handling, cqlhandling, pylexotron,
>>>> sslhandling
>>>> ImportError: No module named cqlshlib
>>>>
>>>> Is there a better way than installing that old package ?
>>>>
>>>> Thanks 
>>>> —
>>>> Cyril Scetbon
>>>>
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> <mailto:user-unsubscr...@cassandra.apache.org>
>> For additional commands, e-mail: user-h...@cassandra.apache.org
>> <mailto:user-h...@cassandra.apache.org>
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra 2.1 on Xenial

[Michael Shuler]

Looked at your error again. The cassandra-stress example appears as if
thrift is disabled, which is the default stress profile. Try
`cassandra-stress write -mode native cql3 ...` for native cql stress runs.

Michael

On 03/22/2018 11:36 PM, Michael Shuler wrote:
> dh_python is a build dependency. The runtime dependency is python.
> 
> https://github.com/apache/cassandra/blob/cassandra-2.1/debian/control#L6
> https://github.com/apache/cassandra/blob/cassandra-2.1/debian/control#L14
> 
> Just upgrading to the latest 2.1.x should fix all these issues your
> having. :)
> 
> Michael
> 
> On 03/22/2018 09:59 PM, Cyril Scetbon wrote:
>> Yeah, I also had to grab a new version of the cassandra-driver which was
>> fixed in 2.1.16 https://issues.apache.org/jira/browse/CASSANDRA-11850
>> otherwise cqlsh would not work with python 2.7.12.
>>
>> I’m surprised dh-python is not a requirement on the Cassandra package in
>> your debian/control 😮
>>
>> I also noticed that I get issues with cassandra-stress on
>> Xenial https://pastebin.com/raw/r2umZXSV, Any idea ? 
>>
>> Bests
>> —
>> Cyril Scetbon
>>
>>> On Mar 19, 2018, at 12:16 PM, Michael Shuler >> <mailto:mich...@pbandjelly.org>> wrote:
>>>
>>> Yep. This was fixed for 2.1.15, 2.2.7, 3.0.6, 3.6 in
>>> https://issues.apache.org/jira/browse/CASSANDRA-10853
>>>
>>> -- 
>>> Kind regards,
>>> Michael
>>>
>>> On 03/18/2018 10:55 PM, Cyril Scetbon wrote:
>>>> Okay I found that when building the package, the new helper dh_python2
>>>> must be used to fix that issue.
>>>>
>>>> —
>>>> Cyril Scetbon
>>>>
>>>>> On Mar 18, 2018, at 11:08 AM, Cyril Scetbon >>>> <mailto:cyril.scet...@free.fr>
>>>>> <mailto:cyril.scet...@free.fr>> wrote:
>>>>>
>>>>> Hey guys,
>>>>>
>>>>> Having to still use Cassandra 2.1, I have installed it on Ubuntu
>>>>> Xenial and I have an issue with cqlsh. I was able to fix it by
>>>>> installing python-support and a fix from 2.1.16. However I’d like to
>>>>> know if there is a way to do it without installing an old package
>>>>> (python-support) on Xenial. dh-python is supposed to have replaced
>>>>> python-support, however cqlsh complains when it’s not installed : 
>>>>>
>>>>> Traceback (most recent call last):
>>>>>   File "/usr/bin/cqlsh", line 121, in 
>>>>>     from cqlshlib import cql3handling, cqlhandling, pylexotron,
>>>>> sslhandling
>>>>> ImportError: No module named cqlshlib
>>>>>
>>>>> Is there a better way than installing that old package ?
>>>>>
>>>>> Thanks 
>>>>> —
>>>>> Cyril Scetbon
>>>>>
>>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>>> <mailto:user-unsubscr...@cassandra.apache.org>
>>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>> <mailto:user-h...@cassandra.apache.org>
>>
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra 2.1 on Xenial

[Michael Shuler]

Well, now I'm a little stumped. I tried native mode with thrift enabled,
wrote one row, so schema is created, then set start_rpc: false,
restarted C*, and native mode fails in the same way. So it's not just
the schema creation phase. I also tried including -port native=9042 and
-schema keyspace="keyspace1", along with some other options, but still
fails for me.

Perhaps some other dev might help us track this down, but I don't see
this as a critical issue with 2.1, so may not get fixed in this branch.
The workaround appears to be to leave port 9160 when using
cassandra-stress on 2.1, even though not using it.

It may be worthwhile to try using stress from a 2.2 or 3.0 tar on a
client machine against the 2.1 cluster and see if that behaves any better.

Michael

On 03/23/2018 08:10 AM, Cyril Scetbon wrote:
> Here is the command I use :
> 
> cassandra-stress user profile=cass_insert_bac.yaml ops\(insert=1\) -mode
> native cql3 user=cassandra password=cassandra -rate threads=1
> 
> Thrift is disabled (start_rpc: False) as I’m not supposed to use thrift
> at all. But I was surprised
> by org.apache.thrift.transport.TTransportException too. Does it mean
> that it doesn’t try to use the native protocol ? 
> 
> I also tried with a command from the documentation and I get exactly the
> same error :
> 
> $ cassandra-stress write n=100k cl=ONE no-warmup -mode native cql3
> user=cassandra password=cassandra
> Exception in thread "main" java.lang.RuntimeException:
> org.apache.thrift.transport.TTransportException:
> java.net.ConnectException: Connection refused
> at
> org.apache.cassandra.stress.settings.StressSettings.getRawThriftClient(StressSettings.java:144)
> at
> org.apache.cassandra.stress.settings.StressSettings.getRawThriftClient(StressSettings.java:110)
> at
> org.apache.cassandra.stress.settings.SettingsSchema.createKeySpacesThrift(SettingsSchema.java:111)
> at
> org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:59)
> at
> org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:205)
> at org.apache.cassandra.stress.StressAction.run(StressAction.java:55)
> at org.apache.cassandra.stress.Stress.main(Stress.java:109)
> Caused by: org.apache.thrift.transport.TTransportException:
> java.net.ConnectException: Connection refused
> at org.apache.thrift.transport.TSocket.open(TSocket.java:187)
> at
> org.apache.thrift.transport.TFramedTransport.open(TFramedTransport.java:81)
> at
> org.apache.cassandra.thrift.TFramedTransportFactory.openTransport(TFramedTransportFactory.java:41)
> at
> org.apache.cassandra.stress.settings.StressSettings.getRawThriftClient(StressSettings.java:124)
> ... 6 more
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.thrift.transport.TSocket.open(TSocket.java:182)
> 
>> On Mar 23, 2018, at 1:00 AM, Michael Shuler > <mailto:mich...@pbandjelly.org>> wrote:
>>
>> Looked at your error again. The cassandra-stress example appears as if
>> thrift is disabled, which is the default stress profile. Try
>> `cassandra-stress write -mode native cql3 ...` for native cql stress runs.
>>
>> Michael
>>
>> On 03/22/2018 11:36 PM, Michael Shuler wrote:
>>> dh_python is a build dependency. The runtime dependency is python.
>>>
>>> https://github.com/apache/cassandra/blob/cassandra-2.1/debian/control#L6
>>> https://github.com/apache/cassandra/blob/cassandra-2.1/debian/control#L14
>>>
>>> Just upgrading to the latest 2.1.x should fix all these issues your
>>> having. :)
>>>
>>> Michael
>>>
>>> On 03/22/2018 09:59 PM, Cyril Scetbon wrote:
>>>> Yeah, I also had to grab a new version of the cassandra-driver which was
>>>> fixed in 2.1.16 https://issues.apache.org/jira/browse/CASSANDRA-11850
>>>> otherwise cqlsh would not work with python 2.7.12.
>>>>
>>>> I’m surprised dh-python is not a requirement on the Cassandra package in
>>>> your debian/control 😮
>>>>
>>>> I also noticed that I get issues with cassandra-stress on
>>>> Xenial https://pastebin.com/raw/r2umZXSV, Any idea ? 
>>>>
>>>> Bests
>>>> —
>&

Re: Cassandra 2.1 on Xenial

[Michael Shuler]

I downloaded the 3.0.16 tar to /tmp on the same host as my 2.1 node was
running (without thrift), and this worked for me:

./tools/bin/cassandra-stress write n=1 -mode native cql3
protocolVersion=3

Michael

On 03/23/2018 09:30 AM, Michael Shuler wrote:
> Well, now I'm a little stumped. I tried native mode with thrift enabled,
> wrote one row, so schema is created, then set start_rpc: false,
> restarted C*, and native mode fails in the same way. So it's not just
> the schema creation phase. I also tried including -port native=9042 and
> -schema keyspace="keyspace1", along with some other options, but still
> fails for me.
> 
> Perhaps some other dev might help us track this down, but I don't see
> this as a critical issue with 2.1, so may not get fixed in this branch.
> The workaround appears to be to leave port 9160 when using
> cassandra-stress on 2.1, even though not using it.
> 
> It may be worthwhile to try using stress from a 2.2 or 3.0 tar on a
> client machine against the 2.1 cluster and see if that behaves any better.
> 
> Michael
> 
> On 03/23/2018 08:10 AM, Cyril Scetbon wrote:
>> Here is the command I use :
>>
>> cassandra-stress user profile=cass_insert_bac.yaml ops\(insert=1\) -mode
>> native cql3 user=cassandra password=cassandra -rate threads=1
>>
>> Thrift is disabled (start_rpc: False) as I’m not supposed to use thrift
>> at all. But I was surprised
>> by org.apache.thrift.transport.TTransportException too. Does it mean
>> that it doesn’t try to use the native protocol ? 
>>
>> I also tried with a command from the documentation and I get exactly the
>> same error :
>>
>> $ cassandra-stress write n=100k cl=ONE no-warmup -mode native cql3
>> user=cassandra password=cassandra
>> Exception in thread "main" java.lang.RuntimeException:
>> org.apache.thrift.transport.TTransportException:
>> java.net.ConnectException: Connection refused
>> at
>> org.apache.cassandra.stress.settings.StressSettings.getRawThriftClient(StressSettings.java:144)
>> at
>> org.apache.cassandra.stress.settings.StressSettings.getRawThriftClient(StressSettings.java:110)
>> at
>> org.apache.cassandra.stress.settings.SettingsSchema.createKeySpacesThrift(SettingsSchema.java:111)
>> at
>> org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:59)
>> at
>> org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:205)
>> at org.apache.cassandra.stress.StressAction.run(StressAction.java:55)
>> at org.apache.cassandra.stress.Stress.main(Stress.java:109)
>> Caused by: org.apache.thrift.transport.TTransportException:
>> java.net.ConnectException: Connection refused
>> at org.apache.thrift.transport.TSocket.open(TSocket.java:187)
>> at
>> org.apache.thrift.transport.TFramedTransport.open(TFramedTransport.java:81)
>> at
>> org.apache.cassandra.thrift.TFramedTransportFactory.openTransport(TFramedTransportFactory.java:41)
>> at
>> org.apache.cassandra.stress.settings.StressSettings.getRawThriftClient(StressSettings.java:124)
>> ... 6 more
>> Caused by: java.net.ConnectException: Connection refused
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at
>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
>> at
>> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>> at
>> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>> at java.net.Socket.connect(Socket.java:589)
>> at org.apache.thrift.transport.TSocket.open(TSocket.java:182)
>>
>>> On Mar 23, 2018, at 1:00 AM, Michael Shuler >> <mailto:mich...@pbandjelly.org>> wrote:
>>>
>>> Looked at your error again. The cassandra-stress example appears as if
>>> thrift is disabled, which is the default stress profile. Try
>>> `cassandra-stress write -mode native cql3 ...` for native cql stress runs.
>>>
>>> Michael
>>>
>>> On 03/22/2018 11:36 PM, Michael Shuler wrote:
>>>> dh_python is a build dependency. The runtime dependency is python.
>>>>
>>>> https://github.com/apache/cassandra/blob/cassandra-2.1/debian/control#L6
>>>> https://github.com/apache/cassandra/blob/cassandra-2.1/debian/control#L14
>>>>
>>>> Just upgrading to the latest 2.1.x should fix all these issues your
>>>> having. :)
>>>>
>>>> Michael
>>>>
>>>> On 03/22/2018 09:59 

Re: Shifting data to DCOS

[Michael Shuler]

On 04/05/2018 09:04 AM, Faraz Mateen wrote:
> 
> For example,  if the table is *data_main_bim_dn_10*, its data directory
> is named data_main_bim_dn_10-a73202c02bf311e8b5106b13f463f8b9. I created
> a new table with the same name through cqlsh. This resulted in creation
> of another directory with a different hash i.e.
> data_main_bim_dn_10-c146e8d038c611e8b48cb7bc120612c9. I copied all data
> from the former to the latter. 
> 
> Then I ran *"nodetool refresh ks1  data_main_bim_dn_10"*. After that I
> was able to access all data contents through cqlsh.
> 
> Now, the problem is, I have around 500 tables and the method I mentioned
> above is quite cumbersome. Bulkloading through sstableloader or remote
> seeding are also a couple of options but they will take a lot of time.
> Does anyone know an easier way to shift all my data to new setup on DC/OS?

For upgrade support from older versions of C* that did not have the hash
on the data directory, the table data dir can be just
`data_main_bim_dn_10` without the appended hash, as in your example.

Give that a quick test to see if that simplifies things for you.

-- 
Kind regards,
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra Hints file corruption

[Michael Shuler]

On 04/09/2018 01:43 PM, Vineet G H wrote:
> Hello All,
> 
> We have a 14 node Cassandra cluster 3.11.1. For some odd reason
> intermittently we see the following error
> 
> ERROR [HintsDispatcher:1] 2018-04-06 16:26:44,423
> CassandraDaemon.java:228 - Exception in thread
> Thread[HintsDispatcher:1,1,main]
> org.apache.cassandra.io.FSReadError: java.io.IOException: Digest
> mismatch exception
> at 
> org.apache.cassandra.hints.HintsReader$BuffersIterator.computeNext(HintsReader.java:298)
> ~[apache-cassandra-3.11.1.jar:3.11.1-SNAPSHOT]

3.11.1-SNAPSHOT? This could be any commit between the 3.11.0 and 3.11.1
releases (usually). If you built this yourself, what commit sha is your
SNAPSHOT jar from and does the git log show it includes commit f919cf4a4?

Generally, using a release artifact is highly suggested, since everyone
knows the code state of the release. No one but yourself can have any
reasonable knowledge of where your cluster is running at code-wise.

> The jar in question has the patch from bug
> 
> https://issues.apache.org/jira/browse/CASSANDRA-13696
> 
> We are able get past the issue by running truncatehints
> 
> 1. Could these new manifestation of the issue? Probably not related to bug 
> above
> 2. Are there any tools which dump hints file content?
> 3. What are the implication of truncatehints? Sounds like there could
> be data loss, but we have quoram for writes and reads, which means we
> should enough replicas to reconstruct the data.
> 
> I am gathering more evidence on the issue would be happy to work with devs
> 
> Regards,
> Vineet

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Latest version and Features

[Michael Shuler]

On 04/11/2018 06:12 PM, Carlos Rolo wrote:
> 
> I blogged about this decision recently
> here: https://blog.pythian.com/what-cassandra-version-should-i-use-2018/

s/it the fact/is the fact/ typo, and possibly not 100% correct on the
statement in that sentence.

There are commits since the last 2.1 & 2.2 releases. Generally, we'll do
a last release with any fixes on the branch, before shuttering
development on older branches. 1.0 and 1.1 had a few commits after the
last releases, but 1.2 and 2.0 both had final releases with any bug
fixes we had in-tree. I expect we'll do the same with 2.1 and 2.2 to
wrap things up nicely.

-- 
Warm regards,
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Logback-tools.xml

[Michael Shuler]

On 04/18/2018 10:39 AM, Abdul Patel wrote:
> 
> I have instakled 3.11.2 and i see 2 new files ..logback-tools.xml and
> -jaas.config ..
> 
> What are they used for ?


logback-tools.xml is the logback configuration for all the tools under
bin/ and tools/bin/, so you could change the root log level for the cli
tools, for example. (logback.xml is for the main Cassandra server
logging config.)

cassandra-jaas.config is the configuration for integrated JMX
authentication added in CASSANDRA-10091.
https://cassandra.apache.org/doc/latest/operating/security.html#cassandra-integrated-auth

-- 
Kind regards,
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: [EXTERNAL] Re: Cassandra downgrade version

[Michael Shuler]

On 04/19/2018 08:48 AM, Durity, Sean R wrote:
> So, the specific question here is whether there is any sstable format
> change between 3.1.0 and 3.11.2. I don’t know if there is.

Here's how to quickly test that:

git clone https://github.com/apache/cassandra.git
cd cassandra/

git checkout cassandra-3.1  #(there was no 3.1.0 release)
ant
./bin/cassandra
./tools/bin/cassandra-stress write n=1
./bin/nodetool flush
ls -l data/data/keyspace1/standard1-*/

pkill -f java
git clean -xdf

git checkout cassandra-3.11.2
# and repeat the above build, start, stress, ls

https://paste.apache.org/I6dr

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: How to configure Cassandra to NOT use SSLv2?

[Michael Shuler]

On 04/20/2018 07:41 AM, Lou DeGenaro wrote:
> Running Cassandra produces the following error message:
> 
> "SSLv2Hello is not a recognized protocol"
> 
> because the JVM being used does not support SSLv2. The JVM does not
> support SSLv2 because "it's a HUGE security risk."
> 
> How does one configure Cassandra to *not* use SSLv2?

See the `server_encryption_options:` and `client_encryption_options:`
sections in conf/cassandra.yaml for the `protocol:` and `cipher_suites:`
configurations. (Defaults are in comments.)

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: How to configure Cassandra to NOT use SSLv2?

[Michael Shuler]

On 04/20/2018 08:46 AM, Lou DeGenaro wrote:
> Could you be more specific?  What does one specify exactly to assure
> SSLv2 is not used for both client-server and server-server
> communications?  Example yaml statements would be wonderful. 

The defaults in cassandra.yaml have only TLS specified in the current
branch HEADs. I'm pretty sure SSLv2/3 removal was a post-POODLE commit.
It's possible you may be on something older - what version are we
talking about?

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: How to configure Cassandra to NOT use SSLv2?

[Michael Shuler]

 the
> cipher_suites option, which allows you 
> to limit the avaliable cipher suites e.g.
> to TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
> (which is a TLS1.2-only cipher suite).
> 
> You can check the offered protocols for your server with an open
> source tool like sslyze (https://github.com/nabla-c0d3/sslyze)
> 
> Marcus Haarmann
> 
> 
> *Von: *"Lou DeGenaro"  <mailto:lou.degen...@gmail.com>>
> *An: *"user"  <mailto:user@cassandra.apache.org>>
> *Gesendet: *Dienstag, 24. April 2018 11:21:06
> *Betreff: *Re: How to configure Cassandra to NOT use SSLv2?
> 
> Can someone please can tell me how to prevent Cassandra 3.0.9 from
> using SSLv2?  Happy to use a newer version of Cassandra if that's
> what's required.
> 
> On Sat, Apr 21, 2018 at 8:30 AM, Lou DeGenaro
> mailto:lou.degen...@gmail.com>> wrote:
> 
> 3.0.9
> 
> On Fri, Apr 20, 2018 at 10:26 PM, Michael Shuler
> mailto:mich...@pbandjelly.org>> wrote:
> 
> On 04/20/2018 08:46 AM, Lou DeGenaro wrote:
> > Could you be more specific?  What does one specify exactly to 
> assure
> > SSLv2 is not used for both client-server and server-server
> > communications?  Example yaml statements would be wonderful. 
> 
> The defaults in cassandra.yaml have only TLS specified in
> the current
> branch HEADs. I'm pretty sure SSLv2/3 removal was a
> post-POODLE commit.
> It's possible you may be on something older - what version
> are we
> talking about?
> 
> -- 
> Michael
> 
> 
> -
> To unsubscribe, e-mail:
> user-unsubscr...@cassandra.apache.org
> <mailto:user-unsubscr...@cassandra.apache.org>
> For additional commands, e-mail:
> user-h...@cassandra.apache.org
> <mailto:user-h...@cassandra.apache.org>
> 
> 
> 
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: com.datastax.driver.core.exceptions.NoHostAvailableException

[Michael Shuler]

host421 != bluej421
My guess is 192.168.3.232 != {host421,bluej421} somewhere.

If DNS hostnames are being used, the DNS infrastructure needs to be spot
on, forward and reverse. If the DNS infrastructure is /etc/hosts, those
hosts entries need to be spot on for the entire cluster, forward and
reverse.

`ping` your hosts from nodes themselves and from remote nodes. Check the
listening ports on all nodes with `netstat`. `telnet $host $port`
locally and remotely. Were the results expected?

Basically, if using DNS, it has to be right everywhere and a lot of
people get DNS wrong.

-- 
Kind regards,
Michael

On 04/26/2018 08:17 AM, Lou DeGenaro wrote:
> version: cassandra-3.0.9
> 
> conf/cassnadra.yaml changes:
> 
>   - seeds: "host421"
> listen_address: host421
> rpc_address: host421
> 
> 
> Java client:
> 
> package database.tools;
> 
> import java.net.InetSocketAddress;
> import java.util.Map;
> import java.util.Map.Entry;
> 
> import com.datastax.driver.core.AuthProvider;
> import com.datastax.driver.core.Cluster;
> import com.datastax.driver.core.PlainTextAuthProvider;
> import com.datastax.driver.core.Session;
> import com.datastax.driver.core.exceptions.NoHostAvailableException;
> 
> public class Creator {
>    
>     private static Cluster cluster;
>     private static Session session = null;
>    
>     private static String dburl = "host421";
>    
>     public static void main(String[] args) {
>         try {
>             AuthProvider auth = new
> PlainTextAuthProvider("cassandra", "cassandra");
>     cluster = Cluster.builder()
>     .withAuthProvider(auth)
>     .addContactPoint(dburl)
>     .build();
>    
>     session = cluster.connect();
>         }
>         catch(NoHostAvailableException e) {
>             e.printStackTrace();
>             Map map = e.getErrors();
>             for(Entry entry :
> map.entrySet()) {
>                 Throwable t = entry.getValue();
>                 t.printStackTrace();
>             }
>         }
>         catch(Exception e) {
>             e.printStackTrace();
>         }
>     }
> 
> }
> 
> 
> Result:
> 
>  INFO | Found Netty's native epoll transport in the classpath, using it
> com.datastax.driver.core.exceptions.NoHostAvailableException: All
> host(s) tried for query failed (tried: bluej421/192.168.3.232:9042
> 
> (com.datastax.driver.core.exceptions.InvalidQueryException:
> unconfigured table schema_keyspaces))
>     at
> 
> com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:227)
>     at
> 
> com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:86)
>     at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1409)
>     at com.datastax.driver.core.Cluster.init(Cluster.java:160)
>     at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:338)
>     at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:311)
>     at com.datastax.driver.core.Cluster.connect(Cluster.java:250)
>     at org.apache.uima.ducc.database.tools.Creator.main(Creator.java:28)
> com.datastax.driver.core.exceptions.InvalidQueryException:
> unconfigured table schema_keyspaces
>     at
> com.datastax.driver.core.Responses$Error.asException(Responses.java:102)
>     at
> 
> com.datastax.driver.core.DefaultResultSetFuture.onSet(DefaultResultSetFuture.java:149)
>     at
> 
> com.datastax.driver.core.DefaultResultSetFuture.onSet(DefaultResultSetFuture.java:167)
>     at
> 
> com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:1013)
>     at
> 
> com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:936)
>     at
> 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>     at
> 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
>     at
> 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
>     at
> 
> io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:254)
>     at
> 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
>     at
> 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
>     at
> 
> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
>     at
> 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
>     at
> 
> io.netty.chan

Re: com.datastax.driver.core.exceptions.NoHostAvailableException

[Michael Shuler]

OK, thanks for the extra info.

Hmm.. `unconfigured table schema_keyspaces`

Seems like an incomplete upgrade to 3.0.9 (and now 3.11.2) from some
earlier version, which used schema_columnfamilies, I think?

-- 
Michael

On 04/26/2018 08:55 AM, Lou DeGenaro wrote:
> Sorry, my mistake.  Everything is bluej421.  I tried  to (but in hind
> sight should not have) edit the append to make the host more generic. 
> The actual experiment uses bluej421 everywhere.
> 
> cqlsh from the same host works fine with the same exact host specified
> as CQLSH_HOST.
> 
> I just now installed apache-cassandra-3.11.2-bin.tar.gz and the problem
> persists.
> 
> 
> 
> On Thu, Apr 26, 2018 at 9:45 AM, Michael Shuler  <mailto:mich...@pbandjelly.org>> wrote:
> 
> host421 != bluej421
> My guess is 192.168.3.232 != {host421,bluej421} somewhere.
> 
> If DNS hostnames are being used, the DNS infrastructure needs to be spot
> on, forward and reverse. If the DNS infrastructure is /etc/hosts, those
> hosts entries need to be spot on for the entire cluster, forward and
> reverse.
> 
> `ping` your hosts from nodes themselves and from remote nodes. Check the
> listening ports on all nodes with `netstat`. `telnet $host $port`
> locally and remotely. Were the results expected?
> 
> Basically, if using DNS, it has to be right everywhere and a lot of
> people get DNS wrong.
> 
> -- 
> Kind regards,
> Michael
> 
> On 04/26/2018 08:17 AM, Lou DeGenaro wrote:
> > version: cassandra-3.0.9
> >
> >     conf/cassnadra.yaml changes:
> >
> >       - seeds: "host421"
> >     listen_address: host421
> >     rpc_address: host421
> >
> >
> > Java client:
> >
> >     package database.tools;
> >
> >     import java.net.InetSocketAddress;
> >     import java.util.Map;
> >     import java.util.Map.Entry;
> >
> >     import com.datastax.driver.core.AuthProvider;
> >     import com.datastax.driver.core.Cluster;
> >     import com.datastax.driver.core.PlainTextAuthProvider;
> >     import com.datastax.driver.core.Session;
> >     import
> com.datastax.driver.core.exceptions.NoHostAvailableException;
> >
> >     public class Creator {
> >    
> >     private static Cluster cluster;
> >     private static Session session = null;
> >    
> >     private static String dburl = "host421";
> >    
> >     public static void main(String[] args) {
> >         try {
> >             AuthProvider auth = new
> >     PlainTextAuthProvider("cassandra", "cassandra");
> >     cluster = Cluster.builder()
> >     .withAuthProvider(auth)
> >     .addContactPoint(dburl)
> >     .build();
> >    
> >     session = cluster.connect();
> >         }
> >         catch(NoHostAvailableException e) {
> >             e.printStackTrace();
> >             Map map = e.getErrors();
> >             for(Entry entry :
> >     map.entrySet()) {
> >                 Throwable t = entry.getValue();
> >                 t.printStackTrace();
> >             }
> >         }
> >         catch(Exception e) {
> >             e.printStackTrace();
> >         }
> >     }
> >
> >     }
> >
> >
> > Result:
> >
> >      INFO | Found Netty's native epoll transport in the classpath,
> using it
> >     com.datastax.driver.core.exceptions.NoHostAvailableException: All
> >     host(s) tried for query failed (tried:
> bluej421/192.168.3.232:9042 <http://192.168.3.232:9042>
> >     <http://192.168.3.232:9042>
> >     (com.datastax.driver.core.exceptions.InvalidQueryException:
> >     unconfigured table schema_keyspaces))
> >     at
> >   
>  
> com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:227)
> >     at
> >   
>  
> com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:86)
> >     at
> com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1409)
> >     at com.datastax.driver.core.C

Re: com.datastax.driver.core.exceptions.NoHostAvailableException

[Michael Shuler]

On 04/26/2018 09:03 AM, Michael Shuler wrote:
> Seems like an incomplete upgrade to 3.0.9 (and now 3.11.2) from some
> earlier version, which used schema_columnfamilies, I think?

Similar error on:
https://datastax-oss.atlassian.net/browse/JAVA-1092

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: com.datastax.driver.core.exceptions.NoHostAvailableException

[Michael Shuler]

On 04/26/2018 09:17 AM, Lou DeGenaro wrote:
> 
> I started fresh and edited the 3.11 cassandra.yaml file.  Here are the
> exact changes:
> 
> diff cassandra.yaml cassandra.yaml.orig
> 425c425
> <   - seeds: "bluej421"
> ---
>>   - seeds: "127.0.0.1"
> 599c599
> < listen_address: bluej421
> ---
>> listen_address: localhost
> 676c676
> < rpc_address: bluej421
> ---
>> rpc_address: localhost
> 
> I made no other changes to Cassandra.  After launching server, cqlsh
> client works.

cqlsh uses embedded python driver. Good check, server is running.

> My java client fails just the same.

Check your java driver version is compatible with your version of
Cassandra. See Andy Tolbert's comment on
https://datastax-oss.atlassian.net/browse/JAVA-1092

The system tables changed in 3.0+.
(I hope this guess is close than my last couple :) )

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: apache-cassandra 2.2.8 rpm

[Michael Shuler]

There is no Apache Cassandra RPM for 2.2.8. If there were, it would be 
basically identical to the Datastax package anyway. The differences 
would be package name and a dependency on python 2.7 in the spec for 
Apache Cassandra. (I used to maintain the Datastax Community packages 
and currently build the Apache Cassandra ones)


The Apache Cassandra project started building RPMS with version 2.2.10 
in the 2.2 series. The RPM packages pick up where Datastax left off 
(although a version or two may have been missed). If you need to stay on 
2.2.8, just use the one you're running now, it's fine.


My suggestion would be the same, if you are planning on upgrading anyway 
- install the latest 2.2 series RPM package, which is currently 2.2.12, 
and follow the NEWS.txt notes as with any upgrade.


Very large warning: test your upgrade on dev/staging cluster. Back up 
configs/data, set up Apache Cassandra RPM repo config, drop the Datastax 
one, and upgrade to latest in your series. The myriad of possible 
package name conflicts were not added to the Apache Cassandra RPMs, so 
upgrade with care - the Apache Cassandra package is not going to 
automagically remove the old community packages, so you'd need to do the 
removal yourself.


Hope that helps!

--
Kind regards,
Michael


On 06/05/2018 10:00 AM, ukevg...@gmail.com wrote:



On 2018/06/05 14:56:24, Carlos Rolo  wrote:

I would recommend migrate to a higher version of Apache Cassandra. Since
Datastax always push some extra patches in their distribution. So I would
go 2.2.8 -> 2.2.9+ at least. Since it's a minor upgrade I would read this
https://github.com/apache/cassandra/blob/cassandra-2.2/NEWS.txt and upgrade
to the 2.2.12.

[image: Pythian]
*Carlos Rolo* | Open Source Consultant | [image: LinkedIn]

*m* +351 918 918 100
r...@pythian.com   *www.pythian.com*

[image: Pythian]


On Tue, Jun 5, 2018 at 3:49 PM, ukevg...@gmail.com 
wrote:




On 2018/06/05 14:28:20, Nicolas Guyomar 
wrote:

Hi,

I believe this rpm was built by Datastax right ?
https://rpm.datastax.com/community/noarch/ is what you seem to be

looking

for
Otherwise newest rpm are here :
https://www.apache.org/dist/cassandra/redhat/22x/

On 5 June 2018 at 16:21, ukevg...@gmail.com  wrote:


Hi everybody,

I am not able to find an RPM package for apache-cassandra 2.2.8

Is there anyone who can share a link I really couldn't find it.

Thank you

Ev

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org



I am trying to migrate from Datastax to apache cassandra.
I already have datastax 2.2.8 installed just trying to migrate to Apache
cassandra 2.2.8

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org




--


--






I will do that if I can't find 2.2.8
Anybody who has apache-cassandra 2.2.8 will save me 3 months ?

Thank you,

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org




-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Installation

[Michael Shuler]

On 07/10/2018 02:48 AM, rajasekhar kommineni wrote:
> Hi Rahul,
> 
> The problem for removing the old links is Cassandra binaries are pointed
> from /usr//bin/, /usr//sbin etc ..
> 
> $ which nodetool 
> /usr/bin/nodetool
> $ which cqlsh
> /usr/bin/cqlsh
> $ which cassandra
> /usr/sbin/cassandra

This is a basic linux usage thing, not really a cassandra problem, but
it's why packages make things simple for general use - the default
/usr/{s}bin locations are in $PATH. If you wish to have nodetool, etc.
in your user's $PATH, just update the user's shell configuration to
include the tar locations.

export CASSANDRA_HOME=
export PATH="$CASSANDRA_HOME/bin:$CASSANDRA_HOME/tools/bin:$PATH"

This can be added to the bottom of ~/.bashrc for persistence. Bonus
points for symlink of generic cassandra_home to versioned one, which is
used for upgrades without messing with PATH env for user and within
configs for Cassandra.

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 2.2.13 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.13.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.2.13
[2]: NEWS.txt:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.13
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 3.0.17 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.17.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.17
[2]: NEWS.txt:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.17
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 3.11.3 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.3.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.3
[2]: NEWS.txt:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.3
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Refering to non-existing node

[Michael Shuler]

On 09/06/2018 01:48 PM, Vlad wrote:
> Hi,
> 3 node cluster, Cassandra 3.9, GossipingPropertyFileSnitch, one DC
> 
> I removed dead node with `nodetool assassinate`. It was also seed node,
> so I removed it from seeds list on two other nodes and restarted them.
> 
> But I still see in log
> `DEBUG [GossipTasks:1] 2018-09-06 18:32:05,149 Gossiper.java:337 -
> Convicting /10.100.129.116 with status LEFT - alive false`
> 
> 
> What does this log mean? How can I get rid of this?

https://twitter.com/faltering/status/559845791741657088

If you *only* used assassinate, without moving through the removal
steps, then the node is still in the system.peers (I think) table on
some or all of the nodes.

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra 2.1.21 ETA?

[Michael Shuler]

On 9/21/18 3:28 AM, Steinmaurer, Thomas wrote:
> 
> is there an ETA for 2.1.21 containing the logback update (security
> vulnerability fix)?

Are you using SocketServer? Is your cluster firewalled?

Feb 2018 2.1->3.11 commits noting this in NEWS.txt:
https://github.com/apache/cassandra/commit/4bbd28a

Feb 2018 trunk (4.0) commit for the library update:
https://github.com/apache/cassandra/commit/c0aa79e

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra 2.1.21 ETA?

[Michael Shuler]

The logback SocketServer and SocketServerReceiver component
vulnerability is with the serialization when using network configuration
for centralized log aggregation. The default Cassandra logback
configuration uses files on disk and does not use these features nor
expose logging to the network. If a user has configured logback to do
logging over the network, then they should consider upgrading the
logback libs. (This has nothing to do with thrift or native protocols.)

Michael

On 10/1/18 3:06 AM, Steinmaurer, Thomas wrote:
> Michael,
> 
> can you please elaborate on your SocketServer question. Is this for Thrift 
> only or also affects the native protocol (CQL)?
> 
> Yes, we basically have iptables rules in place disallowing remote access from 
> machines outside the cluster.
> 
> Thanks again,
> Thomas
> 
>> -Original Message-
>> From: Michael Shuler  On Behalf Of Michael
>> Shuler
>> Sent: Freitag, 21. September 2018 15:49
>> To: user@cassandra.apache.org
>> Subject: Re: Cassandra 2.1.21 ETA?
>>
>> On 9/21/18 3:28 AM, Steinmaurer, Thomas wrote:
>>>
>>> is there an ETA for 2.1.21 containing the logback update (security
>>> vulnerability fix)?
>>
>> Are you using SocketServer? Is your cluster firewalled?
>>
>> Feb 2018 2.1->3.11 commits noting this in NEWS.txt:
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub
>> .com%2Fapache%2Fcassandra%2Fcommit%2F4bbd28a&data=01%7C01
>> %7Cthomas.steinmaurer%40dynatrace.com%7C4b4bcec4c04d4c52f74c08d61
>> fc9e154%7C70ebe3a35b30435d9d677716d74ca190%7C1&sdata=YqHz6ul
>> 55SdPuxHhz5qubNb6MeK1XEjxg63Ttf2v6Uc%3D&reserved=0
>>
>> Feb 2018 trunk (4.0) commit for the library update:
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub
>> .com%2Fapache%2Fcassandra%2Fcommit%2Fc0aa79e&data=01%7C01%
>> 7Cthomas.steinmaurer%40dynatrace.com%7C4b4bcec4c04d4c52f74c08d61fc
>> 9e154%7C70ebe3a35b30435d9d677716d74ca190%7C1&sdata=256fWCvc
>> XDCdFqeQYe618JZfQQDAmV8LVRga4UBvSKs%3D&reserved=0
>>
>> --
>> Michael
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: user-h...@cassandra.apache.org
> 
> The contents of this e-mail are intended for the named addressee only. It 
> contains information that may be confidential. Unless you are the named 
> addressee or an authorized designee, you may not copy or use it, or disclose 
> it to anyone else. If you received it in error please notify us immediately 
> and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) 
> is a company registered in Linz whose registered office is at 4040 Linz, 
> Austria, Freistädterstraße 313
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Help in understanding strange cassandra CPU usage

[Michael Shuler]

On 12/9/18 4:09 AM, Devaki, Srinivas wrote:
> 
> Cassandra Version: 2.2.4

There have been over 300 bug fixes and improvements in the nearly 3
years between 2.2.4 and the latest 2.2.13 release. Somewhere in there
was a GC logging addition as I scanned the changes, which could help
with troubleshooting / tuning. I think that testing the current 2.2
release may also be prudent to rule out some issue that has already been
found & fixed.

https://github.com/apache/cassandra/blob/cassandra-2.2.13/CHANGES.txt#L1-L352
https://github.com/apache/cassandra/blob/cassandra-2.2.13/NEWS.txt#L1-L140

-- 
Kind regards,
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: OpenJDK and Windows Service Error

[Michael Shuler]

On 1/2/19 9:58 AM, Rick L Johnson wrote:
> “Windows could not start the service on Local Computer. For more
> information review the System event log. If this is a non-Microsoft 
> service, contact the service vendor and refer to the server specific 
> error code 1”.

What does the System event log say? What else did you try as a result of
those log entries? etc.

Windows is a best-effort, untested, dev-only platform for the project.
You may need to work line by line through startup scripts, debug, then
offer suggested fixes to the project to keep Windows functional. There
are very few users on the platform, so it's really up to those few users
to keep it working.

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: UNSUBSCRIBE

[Michael Shuler]

Follow the instructions below to unsub.

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Upgrade From 2.0 to 2.1

[Michael Shuler]

On 2/11/19 9:24 AM, shalom sagges wrote:
> I've successfully upgraded a 2.0 cluster to 2.1 on the way to upgrade to
> 3.11 (hopefully 3.11.4 if it'd be released very soon).

Very soon. If not today, it will be up tomorrow. :)

-- 
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 3.11.4 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.4.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.4
[2]: (NEWS.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.4
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 3.0.18 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.18.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.18
[2]: (NEWS.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.18
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 2.2.14 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.14.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.2.14
[2]: (NEWS.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.14
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 2.1.21 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.21.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.1 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.1.21
[2]: (NEWS.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.1.21
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: How to upgrade logback dependency

[Michael Shuler]

https://issues.apache.org/jira/browse/CASSANDRA-14183

2.1 NEWS.txt merged up:
https://github.com/apache/cassandra/blob/cassandra-2.1/NEWS.txt#L21-L28

-- 
Kind regards,
Michael

On 2/12/19 2:49 AM, Oleksandr Shulgin wrote:
> Hi,
> 
> The latest release notes for all versions mention that logback < 1.2.0
> is subject to CVE-2017-5929 and that the logback version is not upgraded.
> E.g: 
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.18
> 
> Indeed, when installing 3.0.18 from the deb package I still see the
> older version:
> 
> # ls -l /usr/share/cassandra/lib/logback*
> -rw-r--r-- 1 root root 280926 Feb  1 18:37
> /usr/share/cassandra/lib/logback-classic-1.1.3.jar
> -rw-r--r-- 1 root root 455041 Feb  1 18:37
> /usr/share/cassandra/lib/logback-core-1.1.3.jar
> 
> Given that I can install a newer logback version, for example, using
> apt-get install liblogback (which currently pulls 1.2.3), how do I make
> sure Cassandra uses the newer one?
> 
> Should I put the newer jars on CLASSPATH before starting the server?
> Examining /usr/share/cassandra/cassandra.in.sh 
> suggests that this is likely to do the trick, but is this the way to go
> or is there a better way?
> Didn't find this documented anywhere.
> 
> Regards,
> -- 
> Alex
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: How to upgrade logback dependency

[Michael Shuler]

On 2/12/19 11:53 AM, Michael Shuler wrote:
> https://issues.apache.org/jira/browse/CASSANDRA-14183
> 
> 2.1 NEWS.txt merged up:
> https://github.com/apache/cassandra/blob/cassandra-2.1/NEWS.txt#L21-L28

I should have included that you can try simply replacing the jars in
lib/ with the newer ones. Logging may break.

If you are not using the logback SocketServer and ServerSocketReceiver
components, the CVE doesn't affect your server with logback 1.1.3.

-- 
Kind regards,
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: How to upgrade logback dependency

[Michael Shuler]

On 2/13/19 2:30 AM, Oleksandr Shulgin wrote:
> On Tue, Feb 12, 2019 at 7:02 PM Michael Shuler  <mailto:mich...@pbandjelly.org>> wrote: 
> 
> If you are not using the logback SocketServer and ServerSocketReceiver
> components, the CVE doesn't affect your server with logback 1.1.3.
> 
> 
> So the idea is that as long as logback.xml doesn't configure any of the
> above, we are fine with the current logback version?

This is my understanding:
The CVE attack vector is over the network when logback is configured to
send/receive logs over the network using the above components. Cassandra
is configured by default to log to local disk and does not use
ServerSocket[Receiver] in the default logback.xml.

I cannot offer an understanding of individual Cassandra user's logback
configurations, so that must be determined by the user. Thus the warning
in NEWS.txt in cassandra-2.1 thru 3.11 branches.

I can offer experience, as I mentioned in CASSANDRA-14183, that some
relatively basic application logback configurations to local disk broke
when the logback-1.2.3 jars were dropped in, since logback internals
changed. This is why the project tries to be careful when updating
libraries in older branches. We did update to logback-1.2.3 in trunk,
since major updates should be expected to possibly need configuration
changes due to library updates. This logback update in trunk also
allowed us to change the default Cassandra local logging to a much
better and non-broken-by-design strategy for users (logback-1.1.x
rotation is pretty broken, and it is intentional).

-- 
Kind regards,
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Oracle: unexpected operator

[Michael Shuler]

On 5/10/19 2:00 PM, Lou DeGenaro wrote:

cassandra-server/bin$ ./nodetool help
./nodetool: 333: [: Oracle: unexpected operator
usage: nodetool [(-u  | --username )]
...


What version of Cassandra? That line number is strange. The string 
"Oracle" along with other garbage seems to be coming from possibly 
cassandra-env.sh version check? I would check what changes you've made 
to these files - something isn't right, nor the same as what was 
originally provided.


(cassandra-3.11)mshuler@hana:~/git/cassandra$ wc -l bin/nodetool
115 bin/nodetool

--
Kind regards,
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

How To Mailing List

[Michael Shuler]

Sub, unsub, and archive links can be found at:
http://cassandra.apache.org/community/

Plain text emails to the list also get a footer appended with similar info:

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Is my range read query behaving strange ?

[Michael Shuler]

(dropped dev@ x-post; user@ was correct)

Possibly #12765, fixed in 2.1.17. Wouldn't hurt to update to latest 2.1.21.

https://issues.apache.org/jira/browse/CASSANDRA-12765
https://github.com/apache/cassandra/blob/cassandra-2.1/CHANGES.txt#L1-L36

Michael

On 6/11/19 9:58 PM, Laxmikant Upadhyay wrote:
Does range query ignore purgable tombstone (which crossed grace period) 
in some cases?


On Tue, Jun 11, 2019, 2:56 PM Laxmikant Upadhyay 
mailto:laxmikant@gmail.com>> wrote:


In a 3 node cassandra 2.1.16 cluster where, one node has old
mutation and two nodes have evict-able (crossed gc grace period)
tombstone produced by TTL. A read range  query with local quorum
return the old mutation as result. However expected result should be
empty. Next time running the same query results no data as expected.
Why this strange behaviour?


*Steps to Reproduce :*
Create a cassandra-2.1.16  3 node cluster. Disable hinted handoff
for each node.

#ccm node1 nodetool ring
Datacenter: datacenter1
==
Address    Rack        Status State   Load            Owns  
      Token

       3074457345618258602
127.0.0.1  rack1       Up     Normal  175.12 KB       100.00%  
       -9223372036854775808
127.0.0.2  rack1       Up   Normal  177.87 KB       100.00%
     -3074457345618258603
127.0.0.3  rack1       Up   Normal  175.13 KB       100.00%
     3074457345618258602


#Connect to cqlsh and set CONISISTENCY LOCAL_QUORUM;

cqlsh> CREATE KEYSPACE IF NOT EXISTS test WITH REPLICATION = {
'class' : 'NetworkTopologyStrategy', 'datacenter1' : 3 };
cqlsh> CREATE TABLE test.table1 (key text, col text, val
text,PRIMARY KEY ((key), col));
cqlsh> ALTER TABLE test.table1  with GC_GRACE_SECONDS = 120;

cqlsh> INSERT INTO test.table1  (key, col, val) VALUES ('key2',
'abc','xyz');

#ccm flush

#ccm node3 stop

cqlsh> INSERT INTO test.table1  (key, col, val) VALUES ('key2',
'abc','xyz') USING TTL 60;

#ccm flush

#wait for 3 min so that the tombstone crosses its gc grace period.

#ccm node3 start

cqlsh> select * from test.table1 where token (key) >
3074457345618258602 and token (key) < -9223372036854775808 ;

  key  | col | val
--+-+-
  key2 | abc | xyz

(1 rows)

#ccm flush
-> Here read repair triggers and the old mutation moves to the one
of the node where tombstone is present (not both the node)


cqlsh> select * from test.vouchers where token (key) >
3074457345618258602 and token (key) < -9223372036854775808 ;

  key | col | val
-+-+-

(0 rows)


-- 


regards,
Laxmikant Upadhyay




-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra migration from 1.25 to 3.x

[Michael Shuler]

First and foremost, read NEWS.txt from your current version to the 
version you wish to upgrade to. There are too may details that you many 
need to be aware of. For instance, in the 2.0.0 Upgrading notes:


https://github.com/apache/cassandra/blob/cassandra-3.11/NEWS.txt#L1169-L1178

I assume you meant 1.2.5, so you're first step is to upgrade to at least 
1.2.9 (I would suggest using latest 1.2.x, which is 1.2.19). Then you 
can to to 2.0.x and up.


Practicing on a scratch cluster is valuable experience. Reading the 
upgrade notes in NEWS.txt is a must.


--
Kind regards,
Michael

On 6/17/19 3:34 AM, Anurag Sharma wrote:

Thanks Alex,

I came across some interesting and efficient ways of upgrading from 1.x 
to 3.x as described in the blog here 
 and 
others. Was curious if someone has open-sourced their custom utility.  :D


Regards
Anurag

On Mon, Jun 17, 2019 at 1:27 PM Oleksandr Shulgin 
mailto:oleksandr.shul...@zalando.de>> wrote:


On Mon, Jun 17, 2019 at 9:30 AM Anurag Sharma
mailto:anurag.rp.sha...@gmail.com>> wrote:


We are upgrading Cassandra from 1.25 to 3.X. Just curious if
there is any recommended open source utility for the same.


Hi,

The "recommended  open source utility" is the Apache Cassandra
itself. ;-)

Given the huge difference between the major versions, though, you
will need a decent amount of planning and preparation to
successfully complete such a migration.  Most likely you will want
to do it in small steps, first upgrading to the latest minor version
in the 1.x series, then making a jump to 2.x, then to 3.0, and only
then to 3.x if you really mean to.  On each upgrade step, be sure to
examine the release notes carefully to understand if there is any
impact for your cluster and/or client applications.  Do have a test
system with preferably identical setup and configuration and execute
the upgrade steps there first to verify your expectations.

Good luck!
--
Alex




-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra tools are missing

[Michael Shuler]

`yum install cassandra-tools`

You should also upgrade to 3.11.4 when you can, there are a number of 
important bug fixes since 3.11.0.


Kind regards,
Michael

On 6/24/19 10:04 PM, Nandakishore Tokala wrote:

HI ,

we installed cassandra-3.11.0 on centos -7  and i see only below tools,
sstableloader   sstablescrub    sstableupgrade  sstableutil 
sstableverify



i am missing lot of other tools , Can any one help me to get other tools

--
Thanks & Regards,
Nanda Kishore



-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra tools are missing

[Michael Shuler]

The "Installation from RPM packages" steps are on the download page[0] - 
your repository configuration doesn't show up in your output, so it 
doesn't appear that the repository was configured properly. The current 
version 3.11.4 is in the main yum repository, so if you specifically 
need 3.11.0, you can wget the package from the archives[1] and `rpm -i 
cassandra-tools-3.11.0-1.noarch.rpm` the package manually.


(Looking at the code block for the /etc/yum.repos.d/cassandra.repo file 
on the download page, it appears that the line breaks are missing from 
the site build magic.. break the lines up as they should be normally, 
sorry about that.)


[0] http://cassandra.apache.org/download/
[1] https://archive.apache.org/dist/cassandra/redhat/311x/

Kind regards,
Michael

On 6/24/19 10:13 PM, Nandakishore Tokala wrote:

yum install cassandra-tools
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
comcast-neto-io 
                                                         | 2.6 kB  00:00:00
comcast-neto-io-x86_64   
                                                        | 2.6 kB  00:00:00

No package cassandra-tools available.
Error: Nothing to do

it is giving below error

On Mon, Jun 24, 2019 at 8:11 PM Michael Shuler <mailto:mich...@pbandjelly.org>> wrote:


`yum install cassandra-tools`

You should also upgrade to 3.11.4 when you can, there are a number of
important bug fixes since 3.11.0.

Kind regards,
Michael

On 6/24/19 10:04 PM, Nandakishore Tokala wrote:
 > HI ,
 >
 > we installed cassandra-3.11.0 on centos -7  and i see only below
tools,
 > sstableloader   sstablescrub    sstableupgrade  sstableutil
 > sstableverify
 >
 >
 > i am missing lot of other tools , Can any one help me to get
other tools
 >
 > --
 > Thanks & Regards,
 > Nanda Kishore


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
<mailto:user-unsubscr...@cassandra.apache.org>
For additional commands, e-mail: user-h...@cassandra.apache.org
<mailto:user-h...@cassandra.apache.org>



--
Thanks & Regards,
Nanda Kishore



-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: cassandra does not start with new systemd version

[Michael Shuler]

Please, submit a JIRA, marking as blocker for fixver 4.0 - attaching a
working service file to the JIRA would be most appreciated. Thanks!

-- 
Michael

On 8/9/19 10:04 AM, a.yats...@rtk-dc.ru wrote:
> Hi.
> 
> After update systemd with  fixed
> vulnerability https://access.redhat.com/security/cve/cve-2018-16888, the
> cassandra service does not start correctly.
> 
> How to fix it? It may be necessary to add a real service unit for systemd ?
> 
> 
> 
> systemctl status cassandra
> ● cassandra.service - LSB: distributed storage system for structured data
>    Loaded: loaded (/etc/rc.d/init.d/cassandra; bad; vendor preset: disabled)
>    Active: failed (Result: resources) since Fri 2019-08-09 17:20:26 MSK;
> 1s ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 2414 ExecStop=/etc/rc.d/init.d/cassandra stop (code=exited,
> status=0/SUCCESS)
>   Process: 2463 ExecStart=/etc/rc.d/init.d/cassandra start (code=exited,
> status=0/SUCCESS)
>  Main PID: 1884 (code=exited, status=143)
> 
> Aug 09 17:20:23 desktop43.example.com systemd[1]: Unit cassandra.service
> entered failed state.
> Aug 09 17:20:23 desktop43.example.com systemd[1]: cassandra.service failed.
> Aug 09 17:20:23 desktop43.example.com systemd[1]: Starting LSB:
> distributed storage system for structured data...
> Aug 09 17:20:23 desktop43.example.com su[2473]: (to cassandra) root on none
> Aug 09 17:20:26 desktop43.example.com cassandra[2463]: Starting
> Cassandra: OK
> Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does
> not belong to service, and PID file is not owned by root. Refusing.
> Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does
> not belong to service, and PID file is not owned by root. Refusing.
> Aug 09 17:20:26 desktop43.example.com systemd[1]: Failed to start LSB:
> distributed storage system for structured data.
> Aug 09 17:20:26 desktop43.example.com systemd[1]: Unit cassandra.service
> entered failed state.
> Aug 09 17:20:26 desktop43.example.com systemd[1]: cassandra.service failed.
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 4.0-alpha1 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache 
Cassandra version 4.0-alpha1.


Apache Cassandra is a fully distributed database. It is the right choice 
when you need scalability and high availability without compromising 
performance.


 http://cassandra.apache.org/

Downloads of source and binary distributions for 4.0-alpha1:


http://www.apache.org/dyn/closer.lua/cassandra/4.0-alpha1/apache-cassandra-4.0-alpha1-bin.tar.gz

http://www.apache.org/dyn/closer.lua/cassandra/4.0-alpha1/apache-cassandra-4.0-alpha1-src.tar.gz

Debian and Redhat configurations

 sources.list:
 deb http://www.apache.org/dist/cassandra/debian 40x main

 yum config:
 baseurl=https://www.apache.org/dist/cassandra/redhat/40x/

See http://cassandra.apache.org/download/ for full install instructions. 
Since this is the first alpha release, it will not be present on the 
download page.


This is an ALPHA version! It is not intended for production use, however 
the project would appreciate your testing and feedback to make the final 
release better. As always, please pay attention to the release notes[2] 
and Let us know[3] if you were to encounter any problem.


Enjoy!

[1]: CHANGES.txt: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-alpha1
[2]: NEWS.txt: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-alpha1

[3]: JIRA: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 2.2.15 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache 
Cassandra version 2.2.15.


Apache Cassandra is a fully distributed database. It is the right choice 
when you need scalability and high availability without compromising 
performance.


 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download 
section:


 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always, 
please pay attention to the release notes[2] and Let us know[3] if you 
were to encounter any problem.


Enjoy!

[1]: CHANGES.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.2.15
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.15

[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 3.0.19 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache 
Cassandra version 3.0.19.


Apache Cassandra is a fully distributed database. It is the right choice 
when you need scalability and high availability without compromising 
performance.


 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download 
section:


 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always, 
please pay attention to the release notes[2] and Let us know[3] if you 
were to encounter any problem.


Enjoy!

[1]: CHANGES.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.19
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.19

[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 3.11.5 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache 
Cassandra version 3.11.5.


Apache Cassandra is a fully distributed database. It is the right choice 
when you need scalability and high availability without compromising 
performance.


 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download 
section:


 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always, 
please pay attention to the release notes[2] and Let us know[3] if you 
were to encounter any problem.


Enjoy!

[1]: CHANGES.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.5
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.5

[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 4.0-alpha2 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache 
Cassandra version 4.0-alpha2.


Apache Cassandra is a fully distributed database. It is the right choice 
when you need scalability and high availability without compromising 
performance.


 http://cassandra.apache.org/

Downloads of source and binary distributions:

http://www.apache.org/dyn/closer.lua/cassandra/4.0-alpha2/apache-cassandra-4.0-alpha2-bin.tar.gz

http://www.apache.org/dyn/closer.lua/cassandra/4.0-alpha2/apache-cassandra-4.0-alpha2-src.tar.gz

Debian and Redhat configurations

 sources.list:
 deb http://www.apache.org/dist/cassandra/debian 40x main

 yum config:
 baseurl=https://www.apache.org/dist/cassandra/redhat/40x/

See http://cassandra.apache.org/download/ for full install instructions.

This is an ALPHA version! It is not intended for production use, however 
the project would appreciate your testing and feedback to make the final 
release better. As always, please pay attention to the release notes[2] 
and let us know[3] if you encounter any problems.


Enjoy!

[1]: CHANGES.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0-alpha2
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0-alpha2

[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Where to get old RPMs?

[Michael Shuler]

On 10/30/19 12:39 PM, Reid Pinchback wrote:

With the latest round of C* updates, the yum repo no longer has
whatever the previous version is.  For environments that try to do
more controlled stepping of release changes instead of just taking
the latest, is there any URL for previous versions of RPMs?  Previous
jars I can find easily enough, but not RPMs.


All the old release artifacts are archived at archive.apache.org. The 
non-latest RPMs are under the redhat/XYx/ directory for whichever major 
version you need.


https://archive.apache.org/dist/cassandra/redhat/

Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 2.2.8 released

[Michael Shuler]

* NOTICE *
This is the first release signed with key 0xA278B781FE4B2BDA by Michael
Shuler. Debian users will need to add the key to `apt-key` and the
process has been updated on
https://wiki.apache.org/cassandra/DebianPackaging and patch created for
source docs.

Either method will work:

curl https://www.apache.org/dist/cassandra/KEYS | sudo apt-key add -

or

sudo apt-key adv --keyserver pool.sks-keyservers.net --recv-key
0xA278B781FE4B2BDA

**

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.8.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt) https://goo.gl/pvdo31
[2]: (NEWS.txt) https://goo.gl/PbDAPY
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.8 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.8.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.8 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt) https://goo.gl/QYFPm1
[2]: (NEWS.txt) https://goo.gl/f9y9ZV
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 3.9 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.9.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.9 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt) https://goo.gl/SCtmhc
[2]: (NEWS.txt) https://goo.gl/brKot5
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Docs Contribution (was: Re: [RELEASE] Apache Cassandra 3.9 released)

[Michael Shuler]

On 09/29/2016 04:08 PM, Dorian Hoxha wrote:
> So how does documentation work? Example: I'm interested in Change Data
> Capture.

The documentation is in-tree, under doc/source, so create a patch and
upload it to a JIRA, just as any source change. :)

The docs on patches do have testing details, so perhaps you might also
add a documentation patch contribution section here that suits what you
are doing a little better for the next person.

http://cassandra.apache.org/doc/latest/development/patches.html

-- 
Kind regards,
Michael

[RELEASE] Apache Cassandra 2.1.16 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.16.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.1 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt) https://goo.gl/Unwb9s
[2]: (NEWS.txt) https://goo.gl/LuZHa5
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: Can not delete record with counter column in a batch.

[Michael Shuler]

On 10/13/2016 08:11 PM, Alexei Levashov wrote:
> Previously I did it in a logged batch without any issues but upgrading
> from Cassandra 1.2.x to 2.1 brings the following Exception message:
> "Error executing batch. Message: Cannot include a counter statement in a
> logged batch"
> 
> Question: 
> It looks like exception thrown from this line:
> 
> if (isLogged() && statement.isCounter()) throw new
> InvalidRequestException("Cannot include a counter statement in a logged
> batch");
> 
> Why does DELETE statement for the table containing counter field return
> isCounter() == true? 
> Is it a bug or expected behavior?

This appears to be expected behavior.

If you look at blame on the line you linked, it was commit ee401cf8
which you can follow to the commit:

https://github.com/apache/cassandra/commit/ee401cf8131a779069805cbe9ef4ab05d4a63b9a

Which notes: CASSANDRA-7351
 https://issues.apache.org/jira/browse/CASSANDRA-7351

It looks like you may use UNLOGGED batch.

-- 
Kind regards,
Michael

Re: cqlsh fails to connect

[Michael Shuler]

It may be possible that you were using the old version of cqlsh? `which
cqlsh` on your upgraded nodes might point to the old install path, or a
copied version somewhere in your $PATH, perhaps.

Doing a fresh install and checking was a good idea, and it does show
that using the current version should be working OK.

-- 
Michael

On 10/28/2016 02:13 PM, Ioannis Zafiropoulos wrote:
> Ok, I tried with a new empty one node cluster of the same DSE version
> and cqlsh works without hiccups.
> So, the whole issue exists because I upgraded from Cassandra 2.1.11.
> 
> The procedure I followed for the upgrade was very simple:
> - nodetool drain (on all nodes)
> - shutdown all nodes
> - Uncompressed the DSE tarball os new version in a new path
> - modified new cassandra.conf
> - started all nodes
> - nodetool upgradesstables 
> 
> The cluster(the one with the problematic cqlsh)  is up and running
> without problems, I am able to connect with DBeaver and via Java.
> What could have gone wrong so that the latest python drivers (3.7.1 &
> 3.6.0) will not let my connect from python?
> 
> Thanks
> 
> On Fri, Oct 28, 2016 at 12:50 PM, Ioannis Zafiropoulos
> mailto:john...@gmail.com>> wrote:
> 
> Hi Rajesh,
> 
> I just tried python 2.711 & 2.7.12 and I get the same error 'invalid
> continuation byte'.
> 
> On Fri, Oct 28, 2016 at 11:53 AM, Rajesh Radhakrishnan
>  > wrote:
> 
> 
> Hi John Z,
> 
> Did you tried running with latest Python 2.7.11 or 2.7.12?
> 
> Kind regards,
> Rajesh Radhakrishnan 
> 
> 
> 
> *From:* Ioannis Zafiropoulos [john...@gmail.com
> ]
> *Sent:* 27 October 2016 22:16
> *To:* user@cassandra.apache.org 
> *Subject:* cqlsh fails to connect
> 
> I upgraded DSE 4.8.9 to 5.0.3, that is, from Cassandra 2.1.11 to
> 3.0.9
> I used DSE 5.0.3 tarball installation. Cassandra cluster is up
> and running OK and I am able to connect through DBeaver.
> 
> Tried a lot of things and cannot connect with cqlsh:
> 
> Connection error: ('Unable to connect to any servers',
> {'x.x.x.x': UnicodeDecodeError('utf8',
> '+\x00\x00H\x08\x00\xf0$+\x00\x00\x10\x7f-\xe7S+\x00\x00`B\xb3\xe5S',
> 6, 7, 'invalid continuation byte')})
> 
> Versions
> 
> $ pip freeze | grep cas
> cassandra-driver==3.6.0
> cassandra-driver-dse==1.0.3
> 
> $ python
> Python 2.7.5 (default, Nov 20 2015, 02:00:19)
> [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)] on linux2
> Type "help", "copyright", "credits" or "license" for more
> information.
> 
> $ cat /etc/redhat-release
> CentOS Linux release 7.2.1511 (Core)
> 
> $ which cqlsh (DSE's cqlsh client)
> /opt/dse/bin/cqlsh
> 
> Tried also
> $ export CQLSH_NO_BUNDLED=false
> 
> Also tried
> --
> Tried to install via pip in a fresh clean box the cqlsh client.
> I ended up with the latest cassandra-driver 3.7.1
> 
> $ pip freeze | grep cas
> cassandra-driver==3.7.1
> 
> $ pip freeze | grep cql
> cql==1.4.0
> cqlsh==5.0.3
> 
> And got this:
> Connection error: ('Unable to connect to any servers',
> {'x.x.x.x': ProtocolError("cql_version '3.3.1' is not supported
> by remote (w/ native protocol). Supported versions: [u'3.4.0']",)})
> 
> Tried to force it:
> $ cqlsh XX.XX.XX.XX --cqlversion="3.4.0"
> Got the original-first error message:
> Connection error: ('Unable to connect to any servers',
> {'x.x.x.x': UnicodeDecodeError('utf8',
> '+\x00\x00H\x08\x00\xf0$+\x00\x00\x10\x7f-\xe7S+\x00\x00`B\xb3\xe5S',
> 6, 7, 'invalid continuation byte')})
> 
> At some point I got this message too, but I don't remember what
> I did:
> Connection error: ('Unable to connect to any servers',
> {'x.x.x.x': DriverException(u'Failed decoding result column
> "table_name" of type varchar: ',)})
> 
> Thank you in advance for you help,
> John Z
> 
> 
> 
> 
> 
> 
> **
> The information contained in the EMail and any attachments is
> confidential and intended solely and for the attention and use
> of the named addressee(s). It may not be disclosed to any other
> person without the express authority of Public Health England,
> or the intended recipient, or both. If you are not the intended
> recipient, you must not disclose, copy, distribute or retain
> this message or any part of it. This footnote also confirms th

Re: Storing videos in cassandra

[Michael Shuler]

Forward thinking, I would also suggest not storing the full URL, just
the video ID of some sort. The application code can create the URL as
needed, using the ID. If the full URL is stored in Cassandra and some
day in the future, the video file storage system needs to be changed,
this would require updating all the records. One could also use multiple
storage systems, based on if the ID has some characteristic..

-- 
Michael

On 11/14/2016 12:00 PM, Oskar Kjellin wrote:
> The actual video is not stored in Cassandra. You need to use a proper origin 
> like s3. 
> 
> Although you can probably store it in Cassandra, it's not a good idea. 
> 
> 
>> On 14 nov. 2016, at 18:02, raghavendra vutti  
>> wrote:
>>
>> Hi,
>>
>>  Just wanted to know How does hulu or netflix store videos in cassandra.
>>
>> Do they just use references to the video files in the form of URL's and 
>> store in the DB??
>>
>> could someone please me on this.
>>
>>
>> Thanks,
>> Raghavendra.

[RELEASE] Apache Cassandra 3.0.10 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.10.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt) https://goo.gl/qplvTw
[2]: (NEWS.txt) https://goo.gl/whvLcU
[3]: https://issues.apache.org/jira/browse/CASSANDRA

RPM builds in-tree now

[Michael Shuler]

I know there are some RPM users out there, so I've committed a redhat/
directory and tested build/install/service on CentOS 7 from the
resulting packages on the following branches:

- cassandra-2.1
- cassandra-2.2
- cassandra-3.0
- cassandra-3.11
- cassandra-3.X
- trunk

I need to work on getting RPMs into distribution via the normal Apache
Cassandra release cycle, similar to deb packages, but currently users
should be able to build their own packages from the branches, now, if
needed.

Patches welcome in JIRA, if there is something not working as expected.

-- 
Kind regards,
Michael

Re: Why does Cassandra recommends Oracle JVM instead of OpenJDK?

[Michael Shuler]

On 12/21/2016 08:38 AM, Eric Evans wrote:
> I don't really have any opinions on Oracle per say, but Cassandra is a
> Free Software project and I would prefer that we not depend on
> commercial software, (and that's kind of what we have here, an
> implicit dependency).

Just a bit of clarification. The debian packages depend on OpenJDK as
the first preference, then the meta-package that may be satisfied by a
custom rolled Oracle-based deb:

  https://github.com/apache/cassandra/blob/trunk/debian/control#L14

I dug through the pseudo packages that RHEL/CentOS provide in the vendor
OpenJDK rpms and selected 'jre' when I committed:

  https://github.com/apache/cassandra/blob/trunk/redhat/cassandra.spec#L23

In both cases, an install of packaged deb or rpm will pull in OpenJDK by
default, unless the user goes out of his/her way to override this.

-- 
Kind regards,
Michael

Re: Cassandra 4.0

[Michael Shuler]

On 01/17/2017 05:43 AM, Artem Rokhin wrote:
> Do you have any estimates for Cassandra 4.0 release?

Follow the dev@ mailing list for info on upcoming release votes and
other release discussion.

http://mail-archives.apache.org/mod_mbox/cassandra-dev/

-- 
Kind regards,
Michael

[RELEASE] Apache Cassandra 3.10 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.10.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a new feature and bug fix release[1] on the 3.X series.
As always, please pay attention to the release notes[2] and Let us
know[3] if you were to encounter any problem.

This is the last tick-tock feature release of Apache Cassandra. Version
3.11.0 will continue bug fixes from this point on the cassandra-3.11
branch in git.

Enjoy!

[1]: (CHANGES.txt) https://goo.gl/J0VghF
[2]: (NEWS.txt) https://goo.gl/00KNVW
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

Re: 'ResultSet' object has no attribute 'column_types'

[Michael Shuler]

On 02/04/2017 03:46 AM, Jonathan Ness wrote:
> We upgraded our Linux test cluster from 3.9 to 3.10 tonight and now we
> are unable to use cqlsh to select rows from any table.
> 
> [cqlsh 5.0.1 | Cassandra 3.10 | CQL spec 3.4.4 | Native protocol v4]
> Use HELP for help.
> cqlsh> select * from veraminetest.hosts;
> 
> *'ResultSet' object has no attribute ‘column_types'*
> *
> *
> I am guessing this is due to some kind of python-related change in 3.10.
>  Is anyone else hitting this?  Thanks.

We've seen this before with multiple versions of the python-driver
installed on the system. `cqlsh` should be using the one installed at
lib/cassandra-driver-internal-only-3.7.0.post0-2481531.zip, but if you
have an older version installed on the system, depending on your setup,
it may try to use it.

https://issues.apache.org/jira/browse/CASSANDRA-12799

-- 
Kind regards,
Michael

Re: How does cassandra achieve Linearizability?

[Michael Shuler]

If you require the best precision you can get, setting up a pair of
stratum 1 ntpd masters in each data center location with a GPS modules
is not terribly complex. Low latency and jitter on servers you manage.
140ms is a long way away network-wise, and I would suggest that was a
poor choice of upstream (probably stratum 2 or 3) source.

As Jonathan mentioned, there's no guarantee from Cassandra, but if you
need as close as you can get, you'll probably need to do it yourself.

(I run several stratum 2 ntpd servers for pool.ntp.org)

-- 
Kind regards,
Michael

On 02/09/2017 06:47 PM, Kant Kodali wrote:
> Hi Justin,
> 
> There are bunch of issues w.r.t to synchronization of clocks when we
> used ntpd. Also the time it took to sync the clocks was approx 140ms
> (don't quote me on it though because it is reported by our devops :) 
> 
> we have multiple clients (for example bunch of micro services are
> reading from Cassandra) I am not sure how one can achieve
> Linearizability by setting timestamps on the clients ? since there is no
> total ordering across multiple clients.
> 
> Thanks!
> 
> 
> On Thu, Feb 9, 2017 at 4:16 PM, Justin Cameron  > wrote:
> 
> Hi Kant,
> 
> Clock synchronization is important - you should ensure that ntpd is
> properly configured on all nodes. If your particular use case is
> especially sensitive to out-of-order mutations it is possible to set
> timestamps on the client side using the
> drivers. 
> https://docs.datastax.com/en/developer/java-driver/3.1/manual/query_timestamps/
> 
> 
> 
> We use our own NTP cluster to reduce clock drift as much as
> possible, but public NTP servers are good enough for most
> uses. 
> https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/
> 
> 
> 
> Cheers,
> Justin
> 
> On Thu, 9 Feb 2017 at 16:09 Kant Kodali  > wrote:
> 
> How does Cassandra achieve Linearizability with “Last write
> wins” (conflict resolution methods based on time-of-day clocks) ?
> 
> Relying on synchronized clocks are almost certainly
> non-linearizable, because clock timestamps cannot be guaranteed
> to be consistent with actual event ordering due to clock skew.
> isn't it?
> 
> Thanks!
> 
> -- 
> 
> Justin Cameron
> 
> Senior Software Engineer | Instaclustr
> 
> 
> 
> 
> This email has been sent on behalf of Instaclustr Pty Ltd
> (Australia) and Instaclustr Inc (USA).
> 
> This email and any attachments may contain confidential and legally
> privileged information.  If you are not the intended recipient, do
> not copy or disclose its content, but please reply to this email
> immediately and highlight the error to the sender and then
> immediately delete the message.
> 
> 

Re: How does cassandra achieve Linearizability?

[Michael Shuler]

On 02/09/2017 07:21 PM, Kant Kodali wrote:
> @Justin I read this article
> http://www.datastax.com/dev/blog/lightweight-transactions-in-cassandra-2-0.
> And it clearly says Linearizable consistency can be achieved with LWT's.
>  so should I assume the Linearizability in the context of the above
> article is possible with LWT's and synchronization of clocks through
> ntpd ? because LWT's also follow Last Write Wins. isn't it? Also another
> question does most of the production clusters do setup ntpd? If so what
> is the time it takes to sync? any idea

I'll let the others talk more intimately about LWT, but as for NTP, the
client machines do take some time to incrementally settle time
adjustments to meet up with the upstreams - they don't just jump time.

> @Micheal Schuler Are you referring to  something like true time as in
> https://static.googleusercontent.com/media/research.google.com/en//archive/spanner-osdi2012.pdf?
>  
> Actually I never heard of setting up GPS modules and how that can be
> helpful. Let me research on that but good point.

Nah, I'm talking much simpler. For instance you could do this with a
raspberry pi:
http://www.satsignal.eu/ntp/Raspberry-Pi-NTP.html

-- 
Michael

> On Thu, Feb 9, 2017 at 5:09 PM, Michael Shuler  <mailto:mich...@pbandjelly.org>> wrote:
> 
> If you require the best precision you can get, setting up a pair of
> stratum 1 ntpd masters in each data center location with a GPS modules
> is not terribly complex. Low latency and jitter on servers you manage.
> 140ms is a long way away network-wise, and I would suggest that was a
> poor choice of upstream (probably stratum 2 or 3) source.
> 
> As Jonathan mentioned, there's no guarantee from Cassandra, but if you
> need as close as you can get, you'll probably need to do it yourself.
> 
> (I run several stratum 2 ntpd servers for pool.ntp.org
> <http://pool.ntp.org>)
> 
> --
> Kind regards,
> Michael
> 
> On 02/09/2017 06:47 PM, Kant Kodali wrote:
> > Hi Justin,
> >
> > There are bunch of issues w.r.t to synchronization of clocks when we
> > used ntpd. Also the time it took to sync the clocks was approx 140ms
> > (don't quote me on it though because it is reported by our devops :)
> >
> > we have multiple clients (for example bunch of micro services are
> > reading from Cassandra) I am not sure how one can achieve
> > Linearizability by setting timestamps on the clients ? since there is no
> > total ordering across multiple clients.
> >
> > Thanks!
> >
> >
> > On Thu, Feb 9, 2017 at 4:16 PM, Justin Cameron  <mailto:jus...@instaclustr.com>
> > <mailto:jus...@instaclustr.com <mailto:jus...@instaclustr.com>>> wrote:
> >
> > Hi Kant,
> >
> > Clock synchronization is important - you should ensure that ntpd is
> > properly configured on all nodes. If your particular use case is
> > especially sensitive to out-of-order mutations it is possible to set
> > timestamps on the client side using the
> > drivers. 
> https://docs.datastax.com/en/developer/java-driver/3.1/manual/query_timestamps/
> 
> <https://docs.datastax.com/en/developer/java-driver/3.1/manual/query_timestamps/>
> > 
> <https://docs.datastax.com/en/developer/java-driver/3.1/manual/query_timestamps/
> 
> <https://docs.datastax.com/en/developer/java-driver/3.1/manual/query_timestamps/>>
> >
> > We use our own NTP cluster to reduce clock drift as much as
> > possible, but public NTP servers are good enough for most
> > uses. 
> https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/
> 
> <https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/>
> > 
> <https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/
> 
> <https://www.instaclustr.com/blog/2015/11/05/apache-cassandra-synchronization/>>
> >
> > Cheers,
> > Justin
> >
> > On Thu, 9 Feb 2017 at 16:09 Kant Kodali  <mailto:k...@peernova.com>
> > <mailto:k...@peernova.com <mailto:k...@peernova.com>>> wrote:
> >
> > How does Cassandra achieve Linearizability with “Last write
> > wins” (conflict resolution methods based on time-of-day clocks) 
> ?
> >
> > Relying on synchronized clocks are almost certainly
> > non

Re: Nodetool cleanup error - cannot run before a node has joined the ring

[Michael Shuler]

By default, yes, nodetool connects to localhost, which your log entries
show. Use `nodetool -h $PRIV_IP cleanup ...` to connect to that private
IP it's listening on. `nodetool help cleanup` for all options.

-- 
Kind regards,
Michael

On 02/10/2017 02:22 PM, Simone Franzini wrote:
> I am running DSE 4.8.7 / Cassandra 2.1.14.
> When I attempt to run nodetool cleanup on any node / any environment we
> are managing, I get the following output:
> 
> Aborted cleaning up atleast one column family in keyspace ,
> check server logs for more information.
> error: nodetool failed, check server logs
> -- StackTrace --
> java.lang.RuntimeException: nodetool failed, check server logs
> at
> org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:294)
> at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:206)
> 
> 
> The server logs do not have any error or warn message, however I see the
> following log line:
> 2017-02-10 14:06:49,931 INFO  [RMI TCP Connection(34)-127.0.0.1]
>  CompactionManager.java:415 - Cleanup cannot run before a node has
> joined the ring
> 
> That is then followed by a line like this, for every single one of our
> keyspaces and tables:
> 2017-02-10 14:06:49,969 INFO  [RMI TCP Connection(34)-127.0.0.1]
>  CompactionManager.java:294 - No sstables for .
> 
> I find the message above a bit suspicious. Of course I do not have any
> node in the process of joining the ring. It looks like nodetool is
> having trouble connecting to the Cassandra instance? Is it trying to
> connect to localhost? We have Cassandra listening on a private IP, not
> on localhost. All other nodetool commands are running fine though. Any
> suggestion with what could be the issue here?
> 
> Thanks,
> Simone Franzini, PhD
> 
> http://www.linkedin.com/in/simonefranzini

[RELEASE] Apache Cassandra 2.1.17 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.17.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.1 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.1.17
[2]: (NEWS.txt)
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.1.17
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

[RELEASE] Apache Cassandra 3.0.11 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.11.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.11
[2]: (NEWS.txt)
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.11
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

[RELEASE] Apache Cassandra 2.2.9 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.9.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.2.9
[2]: (NEWS.txt)
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.9
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

Re: How does cassandra achieve Linearizability?

[Michael Shuler]

gt;>  * new proposal will just get
>>>>> rejected).
>>>>>
>>>>> Effectively paxos removes the
>>>>> ability to use custom
>>>>> timestamps and addresses clock
>>>>> variance by rejecting ballots
>>>>> with timestamps less than what
>>>>> was last seen.  You can learn
>>>>> more by reading through the
>>>>> other comments and code in that
>>>>> file. 
>>>>>
>>>>> Last write wins is a free for
>>>>> all that guarantees you
>>>>> *nothing* except the timestamp
>>>>> is used as a tiebreaker.  Here
>>>>> we acknowledge things like the
>>>>> speed of light as being a real
>>>>> problem that isn’t going away
>>>>> anytime soon.  This problem is
>>>>> sometimes addressed with event
>>>>> sourcing rather than mutating
>>>>> in place.
>>>>>
>>>>> Hope this helps.
>>>>>
>>>>>
>>>>> Jon
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> On Feb 9, 2017, at 5:21 PM,
>>>>>> Kant Kodali >>>>> <mailto:k...@peernova.com>> wrote:
>>>>>>
>>>>>> @Justin I read this article
>>>>>> 
>>>>>> http://www.datastax.com/dev/blog/lightweight-transactions-in-cassandra-2-0
>>>>>> 
>>>>>> <http://www.datastax.com/dev/blog/lightweight-transactions-in-cassandra-2-0>.
>>>>>> And it clearly says
>>>>>> Linearizable consistency can
>>>>>> be achieved with LWT's.  so
>>>>>> should I assume
>>>>>> the Linearizability in the
>>>>>> context of the above article
>>>>>> is possible with LWT's and
>>>>>> synchronization of clocks
>>>>>> through ntpd ? because LWT's
>>>>>> also follow Last Write Wins.
>>>>>> isn't it? Also another
>>>>>> question does most of the
>>>>>> production clusters do setup
>>>>>> ntpd? If so what is the time
>>>>>> it takes to sync? any idea
>>>>>>
>>>>>> @Micheal Schuler Are you
>>>>>> referring to  something like
>>>>>> true time as in
>>>>>> 
>>>>>> https://static.googleusercontent.com/media/research.google.com/en//archive/spanner-osdi2012.pdf
>>>>>> 
>>>>>> <https://static.googleusercontent.com/media/research.google.com/en//archive/spanner-osdi2012.pdf>?
>>>>>>  
>>>>>> Actually I never heard of
>>>>>>   

Re: [RELEASE] Apache Cassandra 3.0.11 released

[Michael Shuler]

This is correct, we use reprepro and leave the old versions in the pool.

I'm not exactly sure what you mean by "put them back to the apt cache",
Julien. The only thing needed for a downgrade is:
  `wget $URL && dpkg -i cassandra*.deb`

If you run lots of servers on a specific version, then I'd suggest
dropping the specific version you need in a local apt repo and use
`dpkg-scanpackages`.

Basically, it's intentional for a) getting users installing the latest
version, b) saving on download size of metadata, and probably most
importantly c) not needing a release manager to maintain a complete
local debian archive in order to scan every old version for every
release forever. We just build and upload the latest with reprepro.

-- 
Kind regards,
Michael

On 02/23/2017 07:28 PM, Murukesh Mohanan wrote:
> This is speculation on my part, but this might be due to the software used
> to set up the repository. reprepro is very simple to use (and so, somewhat
> popular), but it only supports one version of a package at a time. Older
> deb files are not removed, but they do get dropped from the Packages file.
> This repo might be setup using reprepro.
> 
> On Fri, 24 Feb 2017 at 08:29 Julien Anguenot  wrote:
> 
>> Hey,
>>
>> Any reasons why old versions get removed from the Debian repository when a
>> new version gets promoted?
>>
>> For instance, here one would expect to still be able to:
>>
>>   $ apt-get install cassandra=3.0.10
>>
>> But after that release only the latest 3.0.11 is available:
>>
>>
>> http://dl.bintray.com/apache/cassandra/dists/30x/main/binary-amd64/Packages
>>
>> Old versions are still available from there:
>>
>>http://dl.bintray.com/apache/cassandra/pool/main/c/cassandra/ <
>> http://dl.bintray.com/apache/cassandra/pool/main/c/cassandra/>
>>
>> But it requires to manually download and put them back to the apt cache.
>>
>> It is quite handy for point releases when a rollback is required, and
>> possible, because of regressions.
>>
>> Thanks.
>>
>>J.
>>
>> --
>> Julien Anguenot (@anguenot)
>>
>>> On Feb 21, 2017, at 12:03 PM, Michael Shuler 
>> wrote:
>>>
>>> The Cassandra team is pleased to announce the release of Apache
>>> Cassandra version 3.0.11.
>>>
>>> Apache Cassandra is a fully distributed database. It is the right choice
>>> when you need scalability and high availability without compromising
>>> performance.
>>>
>>> http://cassandra.apache.org/
>>>
>>> Downloads of source and binary distributions are listed in our download
>>> section:
>>>
>>> http://cassandra.apache.org/download/
>>>
>>> This version is a bug fix release[1] on the 3.0 series. As always,
>>> please pay attention to the release notes[2] and Let us know[3] if you
>>> were to encounter any problem.
>>>
>>> Enjoy!
>>>
>>> [1]: (CHANGES.txt)
>>>
>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.11
>>> [2]: (NEWS.txt)
>>>
>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.11
>>> [3]: https://issues.apache.org/jira/browse/CASSANDRA
>>>
>>
>> --
> 
> Murukesh Mohanan,
> Yahoo! Japan
> 

Re: A Single Dropped Node Fails Entire Read Queries

[Michael Shuler]

I may be mistaken on the exact configuration option for the timeout
you're hitting, but I believe this may be the general
`request_timeout_in_ms: 1` in conf/cassandra.yaml.

A reasonable timeout for a "node down" discovery/processing is needed to
prevent random flapping of nodes with a super short timeout interval.
Applications should also retry on a host unavailable exception like
this, because in the long run, this should be expected from time to time
for network partitions, node failure, maintenance cycles, etc.

-- 
Kind regards,
Michael

On 03/10/2017 04:07 AM, Shalom Sagges wrote:
> Hi daniel, 
> 
> I don't think that's a network issue, because ~10 seconds after the node
> stopped, the queries were successful again without any timeout issues.
> 
> Thanks!
> 
>  
> Shalom Sagges
> DBA
> T: +972-74-700-4035
> 
>    
> 
>   We Create Meaningful Connections
> 
> 
> 
>  
> 
> On Fri, Mar 10, 2017 at 12:01 PM, Daniel Hölbling-Inzko
>  > wrote:
> 
> Could there be network issues in connecting between the nodes? If
> node a gets To be the query coordinator but can't reach b and c is
> obviously down it won't get a quorum.
> 
> Greetings
> 
> Shalom Sagges  > schrieb am Fr. 10. März 2017 um 10:55:
> 
> @Ryan, my keyspace replication settings are as follows:
> CREATE KEYSPACE mykeyspace WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DC1': '3', 'DC2: '3', 'DC3': '3'}
>  AND durable_writes = true;
> 
> CREATE TABLE mykeyspace.test (
> column1 text,
> column2 text,
> column3 text,
> PRIMARY KEY (column1, column2)
> 
> The query is */select * from mykeyspace.test where
> column1='x';/*
> 
> @Daniel, the replication factor is 3. That's why I don't
> understand why I get these timeouts when only one node drops. 
> 
> Also, when I enabled tracing, I got the following error:
> *Unable to fetch query trace: ('Unable to complete the operation
> against any hosts', {: Unavailable('Error
> from server: code=1000 [Unavailable exception] message="Cannot
> achieve consistency level LOCAL_QUORUM"
> info={\'required_replicas\': 2, \'alive_replicas\': 1,
> \'consistency\': \'LOCAL_QUORUM\'}',)})*
> 
> But nodetool status shows that only 1 replica was down:
> --  Address  Load   Tokens   OwnsHost ID
>   Rack
> DN  x.x.x.235  134.32 MB  256  ?  
> c0920d11-08da-4f18-a7f3-dbfb8c155b19  RAC1
> UN  x.x.x.236  134.02 MB  256  ?  
> 2cc0a27b-b1e4-461f-a3d2-186d3d82ff3d  RAC1
> UN  x.x.x.237  134.34 MB  256  ?  
> 5b2162aa-8803-4b54-88a9-ff2e70b3d830  RAC1
> 
> 
> I tried to run the same scenario on all 3 nodes, and only the
> 3rd node didn't fail the query when I dropped it. The nodes were
> installed and configured with Puppet so the configuration is the
> same on all 3 nodes. 
> 
> 
> Thanks!
> 
>   
> 
> On Fri, Mar 10, 2017 at 10:25 AM, Daniel Hölbling-Inzko
>  > wrote:
> 
> The LOCAL_QUORUM works on the available replicas in the dc.
> So if your replication factor is 2 and you have 10 nodes you
> can still only loose 1. With a replication factor of 3 you
> can loose one node and still satisfy the query.
> Ryan Svihla mailto:r...@foundev.pro>> schrieb
> am Do. 9. März 2017 um 18:09:
> 
> whats your keyspace replication settings and what's your
> query?
> 
> On Thu, Mar 9, 2017 at 9:32 AM, Shalom Sagges
> mailto:shal...@liveperson.com>>
> wrote:
> 
> Hi Cassandra Users, 
> 
> I hope someone could help me understand the
> following scenario:
> 
> Version: 3.0.9
> 3 nodes per DC
> 3 DCs in the cluster. 
> Consistency Local_Quorum. 
> 
> I did a small resiliency test and dropped a node to
> check the availability of the data. 
> What I assumed would happen is nothing at all. If a
> node is down in a 3 nodes DC, Local_Quorum should
> still be satisfied. 
> However, during the ~10 first seconds after stopping
> the service, I got timeout errors (tried it both
> from the client 

[RELEASE] Apache Cassandra 3.0.12 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.12.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt) https://goo.gl/sc8BvB
[2]: (NEWS.txt) https://goo.gl/S5gpKA
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-- 
Warm regards,
Michael Shuler



signature.asc
Description: OpenPGP digital signature

Re: Is there a way to remove a node with Opscenter?

[Michael Shuler]

On 07/07/2015 07:27 PM, Robert Coli wrote:

On Tue, Jul 7, 2015 at 4:39 PM, Sid Tantia
mailto:sid.tan...@baseboxsoftware.com>>
wrote:

I tried both `nodetool remove node ` and `nodetool
decommission` and they both give the error:

nodetool: Failed to connect to '127.0.0.1:7199
' - ConnectException: 'Connection refused’.

Here is what I have tried to fix this:


Instead of that stuff, why not :

1) use lsof to determine what IP is being listened to on 7199 by the
running process?
2) connect to that IP


OP said node was already down/dead:

"Don't forget the hierarchy of node removal in #cassandra: decommission, 
removenode, removenode force, assassinate.  Escalate in that order."


https://twitter.com/faltering/status/559845791741657088

:)
Michael

Re: Cassandra WriteTimeoutException

[Michael Shuler]

On 07/15/2015 02:28 AM, Amlan Roy wrote:

Hi,

I get the following error intermittently while writing to Cassandra.
I am using version 2.1.7. Not sure how to fix the actual issue
without increasing the timeout in cassandra.yaml.




Post your data model, query, and maybe some cluster config basics for 
better help. Increasing the timeout is never a great answer..


--
Kind regards,
Michael

Re: Upgraded to Cassandra 2.2.0 nodes not seeing each other

[Michael Shuler]

On 07/22/2015 04:45 PM, Carlos Scheidecker wrote:

I have a 4 node Cassandra system running on 4 Ubuntu boxes. After
updating to Cassandra 2.2.0 and keeping the same cassandra.yaml file,
the nodes cannot see each other.


What version did you upgrade from?

Usually, when upgrading, it is probably a good idea to start with the 
default cassandra.yaml from the new version (2.2.0 in your case) and 
edit the necessary items from your old version; i.e. num_tokens, 
initial_token, listen_address, broadcast_address, etc. You are perhaps 
missing some sort of default setting that 2.2.0 is looking for?



When I do a nodetool status it only reports as being up the machine
where I had issue the command.

In other words, all the machines cannot communicate to each other any
longer. Nodetool status behave the same on each machine.

I am trying to debug that, hopefully only something on the configuration
that has changed.

Any ideas?


Anything helpful in the system.log on each of your nodes?

Did you follow all the upgrade notes from your previous release to 2.2.0?

https://github.com/apache/cassandra/blob/cassandra-2.2.0/NEWS.txt

--
Kind regards,
Michael

Re: Upgraded to Cassandra 2.2.0 nodes not seeing each other

[Michael Shuler]

ense, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# These properties are used with GossipingPropertyFileSnitch and will
# indicate the rack and dc for this node
dc=DC1
rack=RAC1

# Add a suffix to a datacenter name. Used by the Ec2Snitch and
Ec2MultiRegionSnitch
# to append a string to the EC2 region name.
#dc_suffix=

# Uncomment the following line to make this snitch prefer the internal
ip when possible, as the Ec2MultiRegionSnitch does.
# prefer_local=true

On my cassandra-topology.properties

# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.  See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.  The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# Cassandra Node IP=Data Center:Rack
192.168.1.31=DC1:RAC1
192.168.1.32=DC1:RAC1
192.168.1.33=DC1:RAC1
192.168.1.34=DC1:RAC1

# default for unknown nodes
default=DC1:RAC1





On Wed, Jul 22, 2015 at 5:23 PM, Michael Shuler mailto:mich...@pbandjelly.org>> wrote:

On 07/22/2015 04:45 PM, Carlos Scheidecker wrote:

I have a 4 node Cassandra system running on 4 Ubuntu boxes. After
updating to Cassandra 2.2.0 and keeping the same cassandra.yaml
file,
the nodes cannot see each other.


What version did you upgrade from?

Usually, when upgrading, it is probably a good idea to start with
the default cassandra.yaml from the new version (2.2.0 in your case)
and edit the necessary items from your old version; i.e. num_tokens,
initial_token, listen_address, broadcast_address, etc. You are
perhaps missing some sort of default setting that 2.2.0 is looking for?

When I do a nodetool status it only reports as being up the machine
where I had issue the command.

In other words, all the machines cannot communicate to each
other any
longer. Nodetool status behave the same on each machine.

I am trying to debug that, hopefully only something on the
configuration
that has changed.

Any ideas?


Anything helpful in the system.log on each of your nodes?

Did you follow all the upgrade notes from your previous release to
2.2.0?

https://github.com/apache/cassandra/blob/cassandra-2.2.0/NEWS.txt

--
Kind regards,
Michael

Re: Manual Indexing With Buckets

[Michael Shuler]

On 07/28/2015 07:54 PM, Anuj Wadehra wrote:

Any more thoughts ? Anyone?


You could help others try to help you by including details, as 
previously asked:



*From*:"sean_r_dur...@homedepot.com" 
*Date*:Fri, 24 Jul, 2015 at 5:39 pm

It is a bit hard to follow. Perhaps you could include your proposed
schema (annotated with your size predictions) to spur more discussion.
To me, it sounds a bit convoluted. Why is a “batch” so big (up to 100
million rows)? Is a row in the primary only associated with one batch?

Sean Durity – Cassandra Admin, Big Data Team


--
Kind regards,
Michael

DATASTAX COMMUNITY DEBIAN REPOSITORY ADVISORY - August 6, 2015

[Michael Shuler]

I'm passing this along from the DataStax Support folks.

This shouldn't affect new installs, since the install instruction will 
pull the new expiry, but for users that already have a DSC/DSE Debian 
repository configured, apt-get update/install will warn about the 
expired key after 8/13.


curl -L http://debian.datastax.com/debian/repo_key | sudo apt-key add -

I just tested out updating the key I have in apt-key with the curl 
command below, and update/install seems to work just fine.


Shout if you have any trouble!

Kind regards,
Michael

==

DATASTAX SUPPORT ADVISORY - August 6, 2015
* DSE Debian Repository Key *
* Set to expire August 13, 2015 *
If you have any questions, contact DataStax support.

If you install or upgrade DataStax Community (DSC) or DataStax 
Enterprise (DSE) software using the Aptitude Package Management (APT) 
application, please read this advisory.


The signing key used to sign the DataStax repositories will expire 
August 13th. The purpose of signing the repository is to ensure software 
packages come from a trusted source.  For security reasons the signing 
key used by DataStax is set to expire after a certain number of years.


Required Action:
If you upgrade an existing installation or for some other reason have 
the public repository key installed on your local system, please install 
the new key before August 13th, 2015. The procedure to import the key or 
re-import the new key has not changed.  The key can be updated by 
running the command below on the server that is using the Datastax 
repository.


curl -L http://debian.datastax.com/debian/repo_key | sudo apt-key add -

For more information please refer to our documentation:
http://docs.datastax.com/en/datastax_enterprise/4.7/datastax_enterprise/install/installDEBdse.html 



If you have any questions or concerns please contact DataStax Support.

Thank you,
DataStax Support

Re: 'no such object in table'

[Michael Shuler]

On 08/25/2015 02:19 PM, Jason Lewis wrote:

I'm trying to run nodetool from one node, connecting to another.  I
can successfully connect to the majority of nodes in my ring, but two
nodes throw the following error.

nodetool: Failed to connect to ':7199' NoSuchObjectException: 'no
such object in table'.

Any idea why this is happening?  Misconfiguration?


Possibly. Check those nodes to see if 7199 is listening to only 
localhost or some private IP your client node cannot reach (failed to 
connect). The default is to only listen on localhost, as seen on my machine:


$ netstat -ln | grep 7199
tcp0  0 127.0.0.1:7199  0.0.0.0:*   LISTEN

JMX configuration is set in conf/cassandra-env.sh - please, configure 
JMX security as documented in that file and/or firewall JMX. Check all 
your nodes JMX security configs! :)


--
Kind regards,
Michael

Re: Cassandra certification

[Michael Shuler]

On 10/02/2015 09:11 PM, Renato Perini wrote:

What credibility can have a certification with a non disclosure agreement?


Many (most?) technical certifications require signing and NDA agreeing 
to not disclose the test material. Cisco and RedHat certification tests 
that I have taken both required signing an NDA. Heck, the SAT college 
entrance exam has a non-disclosure, too..


--
Kind regards,
Michael

Re: Node won't go away

[Michael Shuler]

On 10/08/2015 10:27 AM, Robert Wille wrote:

nodetool status doesn’t list it, but its still in system.peers, and
OpsCenter still shows it. When I run nodetool removenode, it says
that it can’t find the node.

How do I completely get rid of it?


https://twitter.com/faltering/status/559845791741657088

"Don't forget the hierarchy of node removal in #cassandra: decommission, 
removenode, removenode force, assassinate.  Escalate in that order."


--
Michael

Re: reiserfs - DirectoryNotEmptyException

[Michael Shuler]

On 10/13/2015 01:58 PM, Modha, Digant wrote:

I am running Cassandra 2.1.10 and noticed intermittent
DirectoryNotEmptyExceptions during repair.  My cassandra data drive
is reiserfs.


Why? I'm genuinely interested in this filesystem selection, since it is
unmaintained, has been dropped from some mainstream linux distributions,
and some may call it "dead". ;)


I noticed that on reiserfs wiki site
https://en.m.wikipedia.org/wiki/ReiserFS#Criticism, it states that
unlink operation is not synchronous. Is that the reason for the
exception below:

ERROR [ValidationExecutor:137] 2015-10-13 00:46:30,759
CassandraDaemon.java:227 - Exception in thread
Thread[ValidationExecutor:137,1,main]

org.apache.cassandra.io.FSWriteError:
java.nio.file.DirectoryNotEmptyException:

at
org.apache.cassandra.io.util.FileUtils.deleteWithConfirm(FileUtils.java:135)

~[apache-cassandra-2.1.10.jar:2.1.10]

<...>

This seems like a reasonable explanation. Using a modern filesystem like
ext4 or xfs would certainly be helpful in getting you within the realm
of a "common" hardware setup.

https://wiki.apache.org/cassandra/CassandraHardware
https://www.safaribooksonline.com/library/view/cassandra-high-performance/9781849515122/ch04s06.html

I think Al Tobey had a slide deck on filesystem tuning for C*, but I 
didn't find it quickly.


--
Kind regards,
Michael

Re: reiserfs - DirectoryNotEmptyException

[Michael Shuler]

On 10/14/2015 05:02 PM, Michael Shuler wrote:

I think Al Tobey had a slide deck on filesystem tuning for C*, but I
didn't find it quickly.


Right! Al included this in his tuning guide:

https://tobert.github.io/pages/als-cassandra-21-tuning-guide.html

--
Michael

Re: Cassandra 2.2.1 stuck at 100% on Windows

[Michael Shuler]

On 10/16/2015 12:02 PM, Alaa Zubaidi (PDF) wrote:

No OOM in any of the log files, and NO long GC at that time.
I attached the last 2 minutes before it hangs until we restart cassandra
after hour an half.


Your logs show gossip issues with some seed nodes. `nodetool gossipinfo` 
on all nodes might be an interesting place to start.


--
Michael

Re: BEWARE https://issues.apache.org/jira/browse/CASSANDRA-9504

[Michael Shuler]

On 10/19/2015 10:55 AM, Graham Sanderson wrote:

If you had Cassandra 2.0.x (possibly before) and upgraded to Cassandra
2.1, you may have had

commitlog_sync: batch

commitlog_sync_batch_window_in_ms: 25


in you cassiandra.yaml

It turned out that this was pretty much broken in 2.0 (i.e. fsyncs just
happened immediately), but fixed in 2.1, *which meant that every
mutation blocked its writer thread for 25ms meaning at 80
mutations/sec/writer thread you’d start DROPPING mutations if your write
timeout is 2000ms.*

This turns out to be a massive problem if you write fast, and the
default commitlog_sync_batch_window_in_ms was changed to 2 ms in 2.1.6
as a way of addressing this (with some suggesting 1ms)

Neither of these changes got much fanfare except an eventual reference
in CHANGES.TXT

With 2.1.9 if you aren’t doing periodic sync, then I think the new
behavior is just to sync whenever the commit logs have a
consistent/complete set of mutations ready.

Note this is hard to diagnose because CPU is idle and pretty much all
latency metrics (except the overall coordinator write) do not count this
time (and you probably weren’t noticing the 25ms write ACK time). It
turned out for us that one of our nodes was getting more writes (> 20k
mutations per second) which was about the magic number… anything shy of
that and everything looked fine, but just by going slightly over, this
node was dropping lots of mutations.


If you would be kind enough to submit a patch to JIRA for NEWS.txt 
(aligned with the right versions you're warning about) that includes the 
info upgrading users might need, that would be great!


--
Kind regards,
Michael

Re: Changing nodes ips

[Michael Shuler]

On 10/20/2015 03:13 PM, Cyril Scetbon wrote:

I'm trying to migrate from ipv4 to ipv6 for those
communications. I tried to follow a similar procedure as the one used
at CASSANDRA-8382
.
When I do the change on the first
node, nodes seems to not see each other, if I trust nodetool :


As mentioned in the linked JIRA, I'm quite certain you will need to do 
all IPv4 -> IPv6 address changes on all nodes at the same time for the 
entire cluster - not one at a time.



_on first node :_

Datacenter: s1
==
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address Load   Tokens  OwnsHost ID
  Rack
*DN  10.10.12.19*?  256 ?
dab24e23-4b42-438e-9070-7994e329e868  i10
*UN* *2a01:c940:a5:2005:0:0:0:18*  244.35 MB  256 ?
03c558ec-add9-4dcd-bf2b-a1b28575e06b  c10


This is likely due to the fact that an IPv6 address will not be really 
able to route directly to an IPv4 address.



_on second node :_
_
_
Datacenter: s1
==
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address   Load   Tokens  Owns (effective)  Host ID
  Rack
*DN  10.10.12.18*  244.24 MB  256 100.0%
 03c558ec-add9-4dcd-bf2b-a1b28575e06b  c10
*UN  10.10.12.19*  244.11 MB  256 100.0%
 dab24e23-4b42-438e-9070-7994e329e868  i10


Because the second node is not aware of the first, since there is no 
communication established.



I can see in the first node logs that it tries to handshake with node
2, however I can't see neither error in node 1 logs nor information in
node 2 logs.

Of course, I'm trying to find a procedure that does not cause any
downtime of the whole cluster.


Doubtful that this is fully possible. It is very similar to the IPv4 
example in the linked JIRA - the 10. and 192.168. networks cannot speak 
to one another, so at least some downtime is to be expected here. Are 
the connecting clients already dual-homed?


That said, there *may* be the possibility to use dual-homed IPv4/v6 
interfaces and using listen_interface and isten_interface_prefer_ipv6: 
true(?) From conf/cassandra.yaml


# If you choose to specify the interface by name and the interface has 
an ipv4 and an ipv6 address
# you can specify which should be chosen using 
listen_interface_prefer_ipv6. If false the first ipv4
# address will be used. If true the first ipv6 address will be used. 
Defaults to false preferring
# ipv4. If there is only one address it will be selected regardless of 
ipv4/ipv6.

listen_address: localhost
# listen_interface: eth0
# listen_interface_prefer_ipv6: false

I'd try out some different methods in a dev env - full listen_address: 
edits and cluster restart; test out listen_interface: and a rolling 
restart, perhaps. Practice your changes in dev, and worst case, you can 
minimize downtime, if it's really necessary. You could be working on a 
network migration no one else has really tried yet :)


--
Kind regards,
Michael

Re: Is replication possible with already existing data?

[Michael Shuler]

On 10/22/2015 10:14 PM, Ajay Garg wrote:

However, CAS11 refuses to come up now.
Following is the error in /var/log/cassandra/system.log ::



ERROR [main] 2015-10-23 03:07:34,242 CassandraDaemon.java:391 - Fatal
configuration error
org.apache.cassandra.exceptions.ConfigurationException: Cannot change
the number of tokens from 1 to 256


Check your cassandra.yaml - this node has vnodes enabled in the 
configuration when it did not, previously. Check all nodes. Something 
changed. Mixed vnode/non-vnode clusters is bad juju.


--
Kind regards,
Michael

Re: nodetool upgradesstables skip major version

[Michael Shuler]

On 10/30/2015 11:12 PM, Xu Zhongxing wrote:

Can I run nodetool upgradesstables after updating a Cassandra 2.0
node directly to Cassandra 3.0?

Or do I have to upgrade to 2.1 and then upgrade to 3.0?


https://github.com/apache/cassandra/blob/cassandra-3.0/NEWS.txt

--
Kind regards,
Michael

Re: Does datastax java driver works with ipv6 address?

[Michael Shuler]

On 11/04/2015 11:17 AM, Dikang Gu wrote:

I have ipv6 only cassandra cluster, and I'm trying to connect to it
using java driver, like:

Inet6Address inet6 = (Inet6Address) 
InetAddress.getByName("2401:db00:0011:60ed:face::0031:");
cluster = Cluster.builder().addContactPointsWithPorts(Arrays.asList(new 
InetSocketAddress(inet6,9042))).build();
session =cluster.connect(CASSANDRA_KEYSPACE);

But it failed to connect to the cassandra, looks like the java driver
does not parse the ipv6 address correctly, exceptions are:




Open a JIRA bug report for the java driver at:

  https://datastax-oss.atlassian.net/browse/JAVA

As for IPv6 testing for Cassandra in general, it has been brought up, 
but little testing is done at this time. If you have some contributions 
to be made in this area, I'm sure they would be greatly appreciated. You 
are in a relatively unique position with an IPv6-only cluster, so your 
input is valuable.



https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20text%20~%20ipv6%20AND%20status%20!%3D%20Resolved

--
Kind regards,
Michael

Re: Generalized download link?

[Michael Shuler]

On 11/16/2015 04:24 PM, John Wong wrote:

Obviously you will get a better answer from someone directly with
datastax... but IMO, I would look to either


The ASF handles the Apache Cassandra download infrastructure, not 
DataStax. (I work for DataStax, fyi)


I believe the OP is asking about links to the mirror redirects from 
http://cassandra.apache.org/download/



* keep the package locally in your own infrastructure. I have had mirror
issue or content unavailable error in the past with other OSS before.

If you can get hold of an NFS server, or a S3 bucket, you will probably
be okay doing bulk roll out more quickly and reliability.


This is good advice and might make things a little faster, if the 
internal mirror is local to the installing clients.



On Mon, Nov 16, 2015 at 3:40 PM, Bryan Cheng mailto:br...@blockcypher.com>> wrote:

Is there a URL available for downloading Cassandra that abstracts
away the mirror selection (eg. just 302's to a mirror URL?) We've
got a few self-configuring Cassandras (for example, the Docker
container our devs use), and using the same mirror for the
containers or for any bulk provisioning operation seems like bad
table manners.


As suggested, your own mirror might be the best route to go, since you 
control the availability and content. The full list of mirrors and 
creating your own mirror docs might be helpful if you want a 
geographically closer mirror, or want to set up your own mirror of a 
subset of software.


http://www.apache.org/mirrors/
http://www.apache.org/info/how-to-mirror.html

I don't know if they or one of the mirrors might provide the ability to 
rsync mirror *only* cassandra to your internal mirror, but even that may 
be too much unnecessary data. Personally, I'd download and throw the 
exact versions of packages you want in dirs on your own web server, and 
just upload new versions for your devs after you've had a quick test or two.


--
Kind regards,
Michael

Re: Devcenter & C* 3.0 Connection Error.

[Michael Shuler]

On 11/16/2015 04:56 PM, Bosung Seo wrote:

Hi guys,

Doesn't Devcenter support C* 3.0?

When I tried to use Devcenter with C* 3.0, I got this error.

The specified host(s) could not be reached.
All host(s) tried for query failed (tried: /{ipaddress}:9042
(com.datastax.driver.core.exceptions.InvalidQueryException: unconfigured
table schema_keyspaces))
unconfigured table schema_keyspaces

Have anyone seen this issue before?


This is the same error I got with OpsCenter on 3.0, so it appears the 
client is attempting to query a table that no longer exists in 3.0+. 
Cassandra 3.0 support is being worked on for both DevCenter and OpsCenter.


--
Kind regards,
Michael

Re: Unable to add nodes / awaiting patch.

[Michael Shuler]

On 12/02/2015 01:54 PM, Jeff Ferland wrote:
> Looks like we’re hit
> by https://issues.apache.org/jira/browse/CASSANDRA-10012. Not knowing a
> better place to ask, when will the next version of 2.1.x Cassandra be
> cut and the following DSE fix cut from there? Could DSE cut an
> in-between version for this fix? Can we patch it into our current
> version of DSE?

Apache Cassandra 2.1.12 just went up for release vote this morning.

http://mail-archives.apache.org/mod_mbox/cassandra-dev/201512.mbox/%3CCALamADLcKJ0_AjToEfwkjZGMLqHNcGdDPMEewBkJ4K0qBEwTjw%40mail.gmail.com%3E

Not sure about the DSE timeline, but you might contact your support
folks with that question, if someone doesn't have that insight here.

I'm also vaguely recalling that you can rip and replace the cassandra
jar in DSE with a newer one(?). Don't quote me on that.. :)

-- 
Michael

Re: Getting a lot of "nothing needed to be retained" INFO

[Michael Shuler]

On 12/03/2015 03:49 PM, John Wong wrote:
> Hi
> 
> I am on Cassandra 1.2.19 and we are running OpsCenter 5.1.4 (and agent
> 5.1.4).
> 
> We recently started to observe high load occurring in our dev cluster.
> There was some small spikes in terms of amount of requests going into
> the cluster so we are not ruling out that possibility.
> 
> What we see is we get memtable filling up, and some gc kicks in. So the
> load is likely contributed by gc. However, we are puzzled why the
> following INFO logs are constantly appearing in our log. We are not sure
> the meanings.
> 
> Do we need to worry about these INFO? We suppress our high load by
> shutting down datastax-agent running on each node. That helped. My
> understanding is the agent adds more load because of the metrics collection.
> 
> INFO 21:42:36,456 Completed flushing; nothing needed to be retained. 
> Commitlog position was ReplayPosition(segmentId=1447227203262,
> position=9710385)
>  INFO 21:43:36,458 Enqueuing flush of
> Memtable-batchlog@1532343528(12360/38070 serialized/live bytes, 120 ops)
>  INFO 21:43:36,459 Writing Memtable-batchlog@1532343528(12360/38070
> serialized/live bytes, 120 ops)
>  INFO 21:43:36,463 Completed flushing; nothing needed to be retained. 
> Commitlog position was ReplayPosition(segmentId=1447227203262,
> position=9795055)

INFO log lines are informational level entries of the actions the node
is performing.

One can configure logging for WARN (and higher priority) logs, if the
INFO lines are not desired.

In conf/log4j-server.properties change the rootLogger from INFO to WARN:

-log4j.rootLogger=INFO,stdout,R
+log4j.rootLogger=WARN,stdout,R

-- 
Kind regards,
Michael

Re: Better setup to start using in production on one server

[Michael Shuler]

On 12/14/2015 05:46 AM, Vladimir Prudnikov wrote:
> I have one dedicated server

This might be OK as a dev/test set up, but defeats the purpose of a
distributed database for production use.

-- 
Kind regards,
Michael

Re: Unable to start Cassandra

[Michael Shuler]

On 12/30/2015 10:56 AM, Nandakishore Arvapaly wrote:
> In one of the cassandra tutorials, it says to set the JAVA_HOME with
> /usr/local/java/jdk1.8.0_65
> I did that but faced the below message when i'm trying to start the
> cassandra with this command "bin/cassandra -f"
> "Cassandra 3.0 and later require Java 8u40 or later"
> 
> Can you please let me know if I have to do something else it to work.

`java -version`
`which java`

-- 
Kind regards,
Michael

Re: opscenter doesn't work with cassandra 3.0

[Michael Shuler]

On 01/06/2016 01:47 AM, Wills Feng wrote:
> Looks like opscenter doesn't support cassandra 3.0?

This is correct. OpsCenter does not support Cassandra >= 3.0.

-- 
Michael

Re: opscenter doesn't work with cassandra 3.0

[Michael Shuler]

On 01/06/2016 10:55 AM, Michael Shuler wrote:
> On 01/06/2016 01:47 AM, Wills Feng wrote:
>> Looks like opscenter doesn't support cassandra 3.0?
> 
> This is correct. OpsCenter does not support Cassandra >= 3.0.

It took me a minute to find the correct document:

http://docs.datastax.com/en/upgrade/doc/upgrade/opscenter/opscCompatibility.html

According to this version table, OpsCenter does not officially support
Cassandra > 2.1.

-- 
Michael

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

[Michael Shuler]

On 01/06/2016 03:57 PM, Peddi, Praveen wrote:
> This blog
> 
> claims Cassandra is now 50% faster. We are obviously not seeing that.

That post compared cassandra-stress write on versions 2.0 and 2.1, each
on a single AWS c3.8xlarge instance, so just be sure to compare apples
to apples in observations.

-- 
Kind regards,
Michael

Re: Using CCM with Opscenter and manual agent installation

[Michael Shuler]

On 01/07/2016 02:09 AM, Giampaolo Trapasso wrote:
> I've configured all the four agents. For example /agent3/ configuration is
> 
> |[Giampaolo]: ~/opscenter/> cat agent3/conf/address.yaml stomp_interface:
> "127.0.0.1" agent_rpc_interface: 127.0.0.3 jmx_host: 127.0.0.3 jmx_port:
> 7300 |

This looks suspect. Each agent is configured for
stomp_interface:"127.0.0.1"?

I'm not sure exactly what that service is, but if all 4 nodes (which are
all really localhost aliases) are attempting to bind to the same IP:port
for that stomp connection, they could be stepping on one another. Should
those be 127.0.0.1 for node1, 127.0.0.12 for node2, etc.?

-- 
Michael