Re: storage engine series

[Michael Shuler]

On 4/29/24 18:23, Jon Haddad wrote:
[4] https://www.youtube.com/live/yj0NQw9DgcE?si=ra1zqusMdSs6vl4T 


Optimizations (upcoming) URL:
[4] https://www.youtube.com/watch?v=MAxQ0QygcKk

:)

Re: Apache archive RedHat repodata

[Michael Shuler]

On 3/18/22 02:31, Stijn Vanden Brande (External) wrote:


The solution should be simply running `createrepo` after the new package 
is added in archive repository to have the correct repo data.


You stated the issue in your initial observation. The contents of 
archive.a.o are an automated ASF-wide rsync from downloads.a.o. There is 
no human to run `createrepo` on the archives. Nor would the addition of 
some sort of post-rsync script work for all Apache Software Foundation 
projects, as this would be error prone. It is a rolling archive of all 
ASF current release artifacts. That's it.


If users have a need to follow a specific version for their clusters, 
the recommendation has always been that they download the specific 
artifacts they need, verify sigs, etc. and toss them on their own web 
server, using the package repository tools they like for deb/rpm 
packages. It is very common for database clusters to have no direct 
internet access at all, and for nodes to have an internal-only web 
server in the infrastructure with their "golden" cluster package 
repository. Test test test some new version in dev or from the public 
repos, then upload those verified packages to the "golden" repo for 
production deployment. Done.


There is no simple way to do this on archive.a.o, so you'll have to do 
this yourself, which ends up being way more stable and predictable in 
the long run. It's a great question that comes up from time to time, it 
just hasn't been asked recently.


Warm regards,
Michael

Re: persist data such that a new container can reuse existing schema and data

[Michael Shuler]

Treat this scenario as any node replacement/restore and test out the 
typical backup methods or bulk data loading to see what works best for 
you. Look at container volume mounts on the host system to possibly 
simplify procedures on the same host system. If moving the container to 
a different host system, general linux data movement utilities are many 
and varied.


Depending on the restore method, schema treatment may differ, for 
instance a snapshot will have a `schema.cql` file contained in the 
snapshot directory that can be used. Other methods may require schema 
creation, then data restore.

https://cassandra.apache.org/doc/latest/operating/backups.html
https://cassandra.apache.org/doc/latest/operating/bulk_loading.html

Hope that gets you started on some things to try. Depending on what you 
choose and specific questions along the way may define where to best get 
help - for docker volume mount strategies, the best help may be some 
docker mailing list or irc channel, for example, but definitely evaluate 
the different cassandra utilities and ask away if you get stuck on one.


Kind regards,
Michael

On 6/13/20 11:57 AM, Manu Chadha wrote:

Hi

I create a Cassandra Container, run it, create schema and add data to 
it. When I later stop the Container and delete it and create a new one 
from the image, the previously created schema and data is lost.


Can I/How can I persist data and schema such that whenever a container 
is created from an image, it picks existing schema and data?


Do would I have to recreate the schema and add data?

Thanks

Sent from Mail  for 
Windows 10




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

Re: Issue with parallel LWT writes (and reads with serial consistency) overwriting data

[Michael Shuler]

There are no table/row locks in Cassandra.

I believe swites from 2 different clients at (essentially precisely) the 
same time on the same table & row have no knowledge of one another. Each 
unique LWT did what was asked of it, read the data and wrote as 
requested. Last write won. This is the definition of eventual 
consistency, and you found an edge case for LWT usage.


There may be other suggestions, but I think the simplest method to get 
as close to a guarantee that your LWT functions as you wish, would be to 
take the parallel access out of the equation. Create a canonical 
user_app that is the only client writing to the user table. app1 and 
app2 make API calls to user_app and wait for its response, with some 
sort of application-level FIFO lock when multiple requests for the same 
row are in flight. The last write to the row still wins, but you control 
the timing to prevent the simultaneous-parallel edge case with LWT.


Michael

On 6/6/20 12:07 AM, Thiranjith Weerasinghe wrote:

Hi Everyone!


We have a 3-node Cassandra cluster (single DC), and a table that get 
accessed (for read/writes) by applications running on separate nodes.


Under heavy load, when both instances of the application are attempting 
to update the same user entry (E.g. add attribute) we observe that 
update from|app1|(running on|node1|succeeded - 
i.e.|ResultSet#wasApplied|returns|true|). However, 
when|app2|(on|node2|reads the data, it is getting stale data 
before|app1|updated it).


I'd like to know why this is happening because LTW with serial 
consistency should prevent this type of inconsistencies. Any help is 
much appreciated! We are using the datastax Java driver.


Thanks!

Thira



*Example:*(based on application logs)

 1. Initially the user has attribute|A|with value|1|
 2. Both|app1|and|app2|are adding new
attributes;|app1|adding|B:2|and|app2|adding|C:3|
 3. |app1|read the correct data into memory, added new attribute|B|and
wrote to Cassandra successfully. The logs show the final attribute
list having|A:1|and|B:2|tuples.
 4. |app2|reads the data, but only see|A:1|(the difference in time
between the logs from|app1|and|app2|is only 2ms; therefore could
have happened in any order).
 5. Once|app2|'s write is completed, the end state only
has|A:1|and|C:2|, which is incorrect.


*More Information*

The (prepared statements that perform) reads and writes to the table 
have the following characteristics: - Write is a LWT (on IF EXISTS 
userid) - Both read and writes use LOCAL_SERIAL consistency level


The table looks like (simple table with userid as the partition key):

CREATE TABLE my_table(userid ascii PRIMARY KEY,attributes map);

The logic within the app when updating the attributes map is:

|

|User user = dao.getUser(userid); user.addNewAttribute("key",
"value"); dao.update(user);|
|







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

Re: Memory usage more than heap memory

[Michael Shuler]

Nodetool isn't really meant for monitoring usage.

There are a number of existing tools to grab and track jvm heap usage. 
Enable JMX and pull the info into something custom, or using a grafana 
template, for instance, which usually uses JMX internally.


ie. this one graphs heap usage historically: 
https://grafana.com/grafana/dashboards/5408


Kind regars,
Michael

On 4/11/20 12:47 PM, HImanshu Sharma wrote:

Hi

I am not worried about page cache. I want to monitor memory pressure, I 
want to check that if heap+non heap usage goes above certain level then 
I can take certain action. But due to this page cache thing, I am not 
sure how to find actual memory usage( heap and off heap). Heap will not 
be more than 8G. Off heap increases with data on disk due to off heap 
storage of bloom filters and index files. I want to know the exact 
amount of memory occupied by off heap components. Nodetool info output 
does not look appropriate to me or I am missing something.


Regards
Himanshu

On Sat, Apr 11, 2020 at 10:13 PM Laxmikant Upadhyay 
mailto:laxmikant@gmail.com>> wrote:


Hi,

You can read section 'OS Page Cache Usage' on
http://cassandra.apache.org/doc/latest/troubleshooting/use_tools.html
Also, don't worry about memory usage (page cache) not decreasing
even if no traffic ...it will come down when required (for example:
a new application needs it when boot up).

On Sat, Apr 11, 2020 at 5:29 PM HImanshu Sharma
mailto:himanshusharma0...@gmail.com>>
wrote:

Hi

I am observing memory usage in top command, but there in RSS it
is showing 18G ( which I think is sum of used memo + page
cache). I want to know how to find how much used by Cassandra
process and how much of it is in page cache. I want this
information because I want to check memory usage for monitoring.

On Sat, Apr 11, 2020 at 9:42 PM Nitan Kainth
mailto:nitankai...@gmail.com>> wrote:

You can look at top command. There is column of memory


Regards,

Nitan

Cell: 510 449 9629 



On Apr 11, 2020, at 11:10 AM, HImanshu Sharma
mailto:himanshusharma0...@gmail.com>> wrote:


Hi

But I see memory not decreasing even if there is no
traffic on cluster. How can I find actual memory usage by
Cassandra process. If it is  OS page cache then how  to
find how much is page  cache and how much is used by process?

Thanks
Himanshu

On Sat, Apr 11, 2020 at 9:07 PM Laxmikant Upadhyay
mailto:laxmikant@gmail.com>>
wrote:

It is OS page cache used during read..your os will
leverage memory if not being used by any other
applications and it improves your read performance.

On Sat, Apr 11, 2020, 12:47 PM HImanshu Sharma
mailto:himanshusharma0...@gmail.com>> wrote:

Hi

I am very new to the use of cassandra. In a
cassandra cluster of 3 nodes, I am observing
memory usage of cassandra process going more than
the heap memor allocated. As I understand,
cassandra allocates off heap memory for bloom
filters, index summary etc.

When I run nodetool info, I see off heap memory
usage around 1.5G, my heap is 8G. So memory usage
should not go above  10G. But in running node it
goes as high as 18G with heavy loads. It comes
down with different loads but always more than 12G.

I would like to know why memory usage is high and
is there way to control it.

Thanks
Himanshu Sharma




-- 


regards,
Laxmikant Upadhyay



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

Re: Memory usage more than heap memory

[Michael Shuler]

For some simple and helpful explanations of the behavior you are 
observing, some ideas on what to look for in monitoring, as well as some 
interesting experiments on the "play" page (last link), have a look at 
https://www.linuxatemyram.com/ - this is general linux memory behavior 
and not unique to this software.


The Cassandra-specific configuration change suggestions may be more harm 
than help, without an understanding the basic kernel behavior. 
Performance benchmarking of your specific workload will be the best way 
to gauge whether configurations help or hurt. One ubiquitous Cassandra 
recommendation is that nodes should have no swap enabled. Paging out/in 
of memory will cause problems, so just don't.


Kind regards,
Michael

On 4/11/20 11:50 AM, Laxmikant Upadhyay wrote:
One more point, if you are worried about high memory usage then read 
about disk_access_mode configuration of Cassandra. By default it will 
cause high memory usage. Setting it to mmap_index_only can help.


On Sat, Apr 11, 2020 at 5:43 PM Laxmikant Upadhyay 
mailto:laxmikant@gmail.com>> wrote:


Hi,

You can read section 'OS Page Cache Usage' on
http://cassandra.apache.org/doc/latest/troubleshooting/use_tools.html
Also, don't worry about memory usage (page cache) not decreasing
even if no traffic ...it will come down when required (for example:
a new application needs it when boot up).

On Sat, Apr 11, 2020 at 5:29 PM HImanshu Sharma
mailto:himanshusharma0...@gmail.com>>
wrote:

Hi

I am observing memory usage in top command, but there in RSS it
is showing 18G ( which I think is sum of used memo + page
cache). I want to know how to find how much used by Cassandra
process and how much of it is in page cache. I want this
information because I want to check memory usage for monitoring.

On Sat, Apr 11, 2020 at 9:42 PM Nitan Kainth
mailto:nitankai...@gmail.com>> wrote:

You can look at top command. There is column of memory


Regards,

Nitan

Cell: 510 449 9629 



On Apr 11, 2020, at 11:10 AM, HImanshu Sharma
mailto:himanshusharma0...@gmail.com>> wrote:


Hi

But I see memory not decreasing even if there is no
traffic on cluster. How can I find actual memory usage by
Cassandra process. If it is  OS page cache then how  to
find how much is page  cache and how much is used by process?

Thanks
Himanshu

On Sat, Apr 11, 2020 at 9:07 PM Laxmikant Upadhyay
mailto:laxmikant@gmail.com>>
wrote:

It is OS page cache used during read..your os will
leverage memory if not being used by any other
applications and it improves your read performance.

On Sat, Apr 11, 2020, 12:47 PM HImanshu Sharma
mailto:himanshusharma0...@gmail.com>> wrote:

Hi

I am very new to the use of cassandra. In a
cassandra cluster of 3 nodes, I am observing
memory usage of cassandra process going more than
the heap memor allocated. As I understand,
cassandra allocates off heap memory for bloom
filters, index summary etc.

When I run nodetool info, I see off heap memory
usage around 1.5G, my heap is 8G. So memory usage
should not go above  10G. But in running node it
goes as high as 18G with heavy loads. It comes
down with different loads but always more than 12G.

I would like to know why memory usage is high and
is there way to control it.

Thanks
Himanshu Sharma




-- 


regards,
Laxmikant Upadhyay



--

regards,
Laxmikant Upadhyay



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

Re: [RELEASE] Apache Cassandra 3.11.6 released

[Michael Shuler]

On 2/21/20 10:28 AM, Michael Shuler wrote:

So a little extra background:
The ASF INFRA team made a change last week to the required release 
location and redirected all requests for the previous required release 
URL to:

   https://downloads.apache.org/cassandra//
   (previous: https://www.apache.org/dist/cassandra// )

This is where projects are required to release artifacts for it to be 
called a release.


The Cassandra project was duplicating the upload of the same tar.gz 
release artifacts to 2 locations - the above location and buried down in 
a maven repository. I understand from Mick, who is beginning to help 
with release management, that the maven upload is undesired. The maven 
tar.gz upload was to facilitate having a place to download the 
hashed/signed artifacts after a release vote (so we don't rely on some 
other non-proper location like someone's laptop or on people.a.o) and 
upload it to the proper release URL above. I don't think it was ever 
intended to be a public user's download location. We have never written 
release email announcements or put this location on the project download 
page.


The 4.0-alpha3 release, as well as the latest round of stable branch 
releases did not upload the tar.gz artifacts to maven. That tar 
shuffling was done in a dist/dev svn repository with some release build 
script changes to better fit policy, and we dropped the maven tarball 
upload, since it is redundant and not a proper release location, per ASF 
release policy. The release publishing doc from the ASF is the main 
thing we've been working from:

   https://apache.org/dev/release-publishing

Last week the Cassandra project updated the main URLs that we put on our 
website from https://www.apache.org/dist/cassandra/ to 
https://downloads.apache.org/cassandra/ per the recommendation of ASF 
INFRA. (It was being redirected anyway.)


For the foreseeable future, the publicly announced location to download 
the latest releases will be: https://www.apache.org/dist/cassandra/


dammit.. scratch that.. this should say:

For the foreseeable future, the publicly announced location to download 
the latest releases will be: https://downloads.apache.org/cassandra/


Michael

As always, if you ever need old releases (only the latest are on the 
main release URL, per policy), the archive URL would be where to find 
those: https://archive.apache.org/dist/cassandra/


I hope that helps! If there is something I got wrong, please let me/us 
know. There are a boatload of ASF rules and documents, and every time I 
go looking for specific info, there are a multitude of doc locations 
that reference specific things, like releases in this case. There are 
links to other docs in the above, such as a maven-specific publish doc.


Man, I'm sorry we pulled the rug out on these - they weren't intended 
for public consumption, as far as I know. I could be completely wrong on 
that, but I believe we were "doing it wrong" as a project, once Mick 
started digging in and helping out.


My best advice is follow what is on the project download page and in the 
release announcement emails. These may change things from time to time.


Kind regards,
Michael

On 2/21/20 9:10 AM, Chad Helms wrote:
Well, that's where they've all been before.  All our automation is 
pulling them from there.  Can you point me to the details of this 
change you mentioned, so we can look at what changes we'll need to 
make and additional thing's we'll have to proxy behind our firewall.


All the 4.0-alpha releases (1 & 2) are also there, btw.

On 2/21/20, 9:02 AM, "Michael Shuler"  wrote:

 Why?
 This release adjusted the location of the tar artifacts, so they 
were

 published to the normal recommended dist/release location and not
 included in maven, where I understand they are not desired to be 
there.

 Kind regards,
 Michael
 On 2/21/20 8:18 AM, Chad Helms wrote:
 > Can we get "apache-cassandra:3.11.6:bin.tar.gz" artifact 
published to maven central too, please?

 >
     > On 2/14/20, 5:28 PM, "Michael Shuler"  wrote:
 >
 >  The Cassandra team is pleased to announce the release of 
Apache

 >  Cassandra version 3.11.6.
 >
 >  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!
  

Re: [RELEASE] Apache Cassandra 3.11.6 released

[Michael Shuler]

So a little extra background:
The ASF INFRA team made a change last week to the required release 
location and redirected all requests for the previous required release 
URL to:

  https://downloads.apache.org/cassandra//
  (previous: https://www.apache.org/dist/cassandra// )

This is where projects are required to release artifacts for it to be 
called a release.


The Cassandra project was duplicating the upload of the same tar.gz 
release artifacts to 2 locations - the above location and buried down in 
a maven repository. I understand from Mick, who is beginning to help 
with release management, that the maven upload is undesired. The maven 
tar.gz upload was to facilitate having a place to download the 
hashed/signed artifacts after a release vote (so we don't rely on some 
other non-proper location like someone's laptop or on people.a.o) and 
upload it to the proper release URL above. I don't think it was ever 
intended to be a public user's download location. We have never written 
release email announcements or put this location on the project download 
page.


The 4.0-alpha3 release, as well as the latest round of stable branch 
releases did not upload the tar.gz artifacts to maven. That tar 
shuffling was done in a dist/dev svn repository with some release build 
script changes to better fit policy, and we dropped the maven tarball 
upload, since it is redundant and not a proper release location, per ASF 
release policy. The release publishing doc from the ASF is the main 
thing we've been working from:

  https://apache.org/dev/release-publishing

Last week the Cassandra project updated the main URLs that we put on our 
website from https://www.apache.org/dist/cassandra/ to 
https://downloads.apache.org/cassandra/ per the recommendation of ASF 
INFRA. (It was being redirected anyway.)


For the foreseeable future, the publicly announced location to download 
the latest releases will be: https://www.apache.org/dist/cassandra/


As always, if you ever need old releases (only the latest are on the 
main release URL, per policy), the archive URL would be where to find 
those: https://archive.apache.org/dist/cassandra/


I hope that helps! If there is something I got wrong, please let me/us 
know. There are a boatload of ASF rules and documents, and every time I 
go looking for specific info, there are a multitude of doc locations 
that reference specific things, like releases in this case. There are 
links to other docs in the above, such as a maven-specific publish doc.


Man, I'm sorry we pulled the rug out on these - they weren't intended 
for public consumption, as far as I know. I could be completely wrong on 
that, but I believe we were "doing it wrong" as a project, once Mick 
started digging in and helping out.


My best advice is follow what is on the project download page and in the 
release announcement emails. These may change things from time to time.


Kind regards,
Michael

On 2/21/20 9:10 AM, Chad Helms wrote:

Well, that's where they've all been before.  All our automation is pulling them 
from there.  Can you point me to the details of this change you mentioned, so 
we can look at what changes we'll need to make and additional thing's we'll 
have to proxy behind our firewall.

All the 4.0-alpha releases (1 & 2) are also there, btw.

On 2/21/20, 9:02 AM, "Michael Shuler"  wrote:

 Why?
 
 This release adjusted the location of the tar artifacts, so they were

 published to the normal recommended dist/release location and not
 included in maven, where I understand they are not desired to be there.
 
 Kind regards,

 Michael
 
 On 2/21/20 8:18 AM, Chad Helms wrote:

 > Can we get "apache-cassandra:3.11.6:bin.tar.gz" artifact published to 
maven central too, please?
 >
     > On 2/14/20, 5:28 PM, "Michael Shuler"  wrote:
 >
 >  The Cassandra team is pleased to announce the release of Apache
 >  Cassandra version 3.11.6.
 >
 >  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.6
 >  [2]: NEWS.txt
 >  
https://gitbox.apache.org

Re: [RELEASE] Apache Cassandra 3.11.6 released

[Michael Shuler]

Why?

This release adjusted the location of the tar artifacts, so they were 
published to the normal recommended dist/release location and not 
included in maven, where I understand they are not desired to be there.


Kind regards,
Michael

On 2/21/20 8:18 AM, Chad Helms wrote:

Can we get "apache-cassandra:3.11.6:bin.tar.gz" artifact published to maven 
central too, please?

On 2/14/20, 5:28 PM, "Michael Shuler"  wrote:

 The Cassandra team is pleased to announce the release of Apache
 Cassandra version 3.11.6.
 
 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.6
 [2]: NEWS.txt
 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.6
 [3]: https://issues.apache.org/jira/browse/CASSANDRA
 
 -

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



-
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: apt error 'Protocol "http" not supported or disabled in libcurl'

[Michael Shuler]

I committed a change in svn to switch the redirect from http to https. I 
don't know how long that takes to hit the downloads, but that may fix 
it. If it does not fix it, I would open a JIRA and ping someone on dev@ 
or the #cassnadra-dev slack channel.


mshuler@hana:~/svn/cassandra-dist$ svn diff
Index: debian/.htaccess
===
--- debian/.htaccess(revision 38111)
+++ debian/.htaccess(working copy)
@@ -1,2 +1,2 @@
 RedirectMatch ^/~eevans/debian(.*) 
http://wiki.apache.org/cassandra/DebianPackaging
-RedirectMatch permanent (.*)cassandra/debian/(.*) 
http://dl.bintray.com/apache/cassandra/$2
+RedirectMatch permanent (.*)cassandra/debian/(.*) 
https://dl.bintray.com/apache/cassandra/$2


Michael

On 2/16/20 11:51 AM, Michael Shuler wrote:
Yeah, ASF INFRA is making download redirect changes on a weekend without 
anyone testing.. got a notice on the project private@ list that there 
were several days to verify and make changes, and my downloads are 
broken now, as well...


c'est la vie...

If you point directly to the bintray urls, it will work. Apt won't use a 
protocol redirect downgrade from https -> http.


Michael

On 2/16/20 11:22 AM, Shaoting Cheng wrote:

Hi experts

I followed the instruction to install Cassandra on the Ubuntu-16.04. 
http://cassandra.apache.org/download/

But `apt-get update` returned the error
===
root@LSW-209:~# apt-get update
...
Ign:6 https://downloads.apache.org/cassandra/debian 311x InRelease
Ign:12 https://downloads.apache.org/cassandra/debian 311x Release
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages
Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 
Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all 
Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages
Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 
Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all 
Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages
Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 
Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all 
Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages
Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 
Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all 
Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages
Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 
Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all 
Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Err:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages

  Protocol "http" not supported or disabled in libcurl
Fetched 109 kB in 8s (12.9 kB/s)
Reading package lists... Done
W: The repository 'http://www.apache.org/dist/cassandra/debian 311x 
Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user 
configuration details.
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/binary-amd64/Packages  Protocol 
"http" not supported or disabled in libcurl
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/binary-i386/Packages  Protocol 
"http" not supported or disabled in libcurl
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/binary-all/Packages  Protocol 
"http" not supported or disabled in libcurl
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/i18n/Translation-en_US  Protocol 
"http" not supported or disabled in libcurl
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/i18n/Translation-en  Protocol 
"http" not supported or disabled in libcurl
E: Some index files failed to download. They have been ignored, or old 
ones used ins

Re: apt error 'Protocol "http" not supported or disabled in libcurl'

[Michael Shuler]

Yeah, ASF INFRA is making download redirect changes on a weekend without 
anyone testing.. got a notice on the project private@ list that there 
were several days to verify and make changes, and my downloads are 
broken now, as well...


c'est la vie...

If you point directly to the bintray urls, it will work. Apt won't use a 
protocol redirect downgrade from https -> http.


Michael

On 2/16/20 11:22 AM, Shaoting Cheng wrote:

Hi experts

I followed the instruction to install Cassandra on the Ubuntu-16.04. 
http://cassandra.apache.org/download/

But `apt-get update` returned the error
===
root@LSW-209:~# apt-get update
...
Ign:6 https://downloads.apache.org/cassandra/debian 311x InRelease
Ign:12 https://downloads.apache.org/cassandra/debian 311x Release
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages

Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages

Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages

Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages

Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Ign:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages

Ign:14 https://downloads.apache.org/cassandra/debian 311x/main i386 Packages
Ign:15 https://downloads.apache.org/cassandra/debian 311x/main all Packages
Ign:16 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en_US
Ign:17 https://downloads.apache.org/cassandra/debian 311x/main 
Translation-en
Err:13 https://downloads.apache.org/cassandra/debian 311x/main amd64 
Packages

  Protocol "http" not supported or disabled in libcurl
Fetched 109 kB in 8s (12.9 kB/s)
Reading package lists... Done
W: The repository 'http://www.apache.org/dist/cassandra/debian 311x 
Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user 
configuration details.
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/binary-amd64/Packages  Protocol 
"http" not supported or disabled in libcurl
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/binary-i386/Packages  Protocol 
"http" not supported or disabled in libcurl
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/binary-all/Packages  Protocol 
"http" not supported or disabled in libcurl
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/i18n/Translation-en_US  Protocol 
"http" not supported or disabled in libcurl
E: Failed to fetch 
https://downloads.apache.org/cassandra/debian/dists/311x/main/i18n/Translation-en  Protocol 
"http" not supported or disabled in libcurl
E: Some index files failed to download. They have been ignored, or old 
ones used instead.

===

Here is the information of my Server, apt, curl

OS
===
Linux LSW-209.58.184.97 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 
10:45:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

==

curl
===
curl 7.47.0 (x86_64-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.4.10 
zlib/1.2.8 libidn/1.32 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps 
pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM 
NTLM_WB SSL libz TLS-SRP UnixSockets

===

apt-get
===
apt 1.2.27 (amd64)
Supported modules:
*Ver: Standard .deb
*Pkg:  Debian dpkg interface (Priority 30)
Pkg:  Debian APT solver interface (Priority -1000)
S.L: 'deb' Debian binary tree
S.L: 'deb-src' Debian source tree
Idx: Debian Source Index
Idx: Debian Package Index
Idx: Debian Translation Index
Idx: Debian dpkg status file
Idx: Debian deb 

[RELEASE] Apache Cassandra 3.11.6 released

[Michael Shuler]

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


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.6
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.6

[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.20 released

[Michael Shuler]

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


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.20
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.20

[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.16 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache 
Cassandra version 2.2.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.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.16
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.16

[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: [EXTERNAL] Cassandra 3.11.X upgrades

[Michael Shuler]

On 2/12/20 12:58 PM, Durity, Sean R wrote:

Check the readme.txt for any upgrade notes


Just a quick correction:

NEWS.txt (upgrade (and other important) notes)
CHANGES.txt (changelog with JIRAs)

This is why we list links to these two files in the release announcements.

--
Kind regards,
Michael

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

Re: Overload because of hint pressure + MVs

[Michael Shuler]

That JIRA still says Open, so no, it has not been fixed (unless there's 
a fixed duplicate in JIRA somewhere).


For clarification, you could update that ticket with a comment including 
your environmental details, usage of MV, etc. I'll bump the priority up 
and include some possible branchX fixvers.


Michael

On 2/7/20 10:53 AM, Surbhi Gupta wrote:

Hi,

We are getting hit by the below bug.
Other than lowering hinted_handoff_throttle_in_kb to 100 any other work 
around ?


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

Any idea if it got fixed in later version.
We are on Open source Cassandra 3.11.1  .

Thanks
Surbhi




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

Re: Query timeouts after Cassandra Migration

[Michael Shuler]

Did you copy the tokens from cluster1 to new cluster2? Same Cassandra 
version, same instance type/size? What to the logs say on cluster2 that 
look different from the cluster1 norm? There are a number of possible 
`nodetool` utilities that may help see what is happening on new cluster2.


Michael

On 2/6/20 8:09 AM, Ankit Gadhiya wrote:

Hi Folks,

I recently migrated Cassandra keyspace data from one Azure cluster (3 
Nodes) to another (3 nodes different region) using simple sstable copy. 
Post this , we are observing overall response time has increased and 
timeouts every 20 mins.


Has anyone faced such in their experiences ?
Do I need to copy anything from system*
Anything wrt statistics/cache ?

Your time and responses on this are much appreciated.


Thanks & Regards,
Ankit
--
*Thanks & Regards,*
*Ankit Gadhiya*



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

Re: Running select against cassandra

[Michael Shuler]

You'll have to be more specific. What is your table schema and what is 
the SELECT query? What is the normal response time?


As a basic guide for your general question, if the query is something 
sort of irrelevant that should be stored some other way, like a total 
row count, or most any SELECT that requires ALLOW FILTERING, you're 
doing it wrong and should re-evaluate your data model.


1 query per minute is a minuscule fraction of the basic capacity of 
queries per minute that a Cassandra cluster should be able to handle 
with good data modeling and table-relevant query. All depends on the 
data model and query.


Michael

On 2/6/20 12:20 PM, Abdul Patel wrote:

Hi,

Is it advisable to run select query to fetch every minute to grab data 
from cassandra for reporting purpose, if no then whats the alternative?





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

Re: Cassandra OS Patching.

[Michael Shuler]

That is some good info. To add just a little more, knowing what the 
pending security updates are for your nodes helps in knowing what to do 
after. Read the security update notes from your vendor.


Java or Cassandra update? Of course the service needs restarted - 
rolling upgrade and restart the `cassandra` service as usual.


Linux kernel update? Node needs a full reboot, so follow a rolling 
reboot plan.


Other OS updates? Most can be done while not affecting Cassandra. For 
instance, an OpenSSH security update to patch some vulnerability should 
most certainly be done as soon as possible, and the node updates can be 
even be in parallel without causing any problems with the JVM or 
Cassandra service. Most intelligent package update systems will install 
the update and restart the affected service, in this hypothetical case 
`sshd`.


Michael

On 1/30/20 3:56 AM, Erick Ramirez wrote:
There is no need to shutdown the application because you should be able 
to carry out the operating system upgraded without an outage to the 
database particularly since you have a lot of nodes in your cluster.


Provided your cluster has sufficient capacity, you might even have the 
ability to upgrade multiple nodes in parallel to reduce the upgrade 
window. If you decide to do nodes in parallel and you fully understand 
the token allocations and where the nodes are positioned in the ring in 
each DC, make sure you only upgrade nodes which are at least 5 nodes 
"away" to the right so you know none of the nodes would have overlapping 
token ranges and they're not replicas of each other.


Other points to consider are:

  * If a node goes down (for whatever reason), I suggest you upgrade the
OS on the node before bringing back up. It's already down so you
might as well take advantage of it since you have so many nodes to
upgrade.
  * Resist the urge to run nodetool decommission or nodetool removenode
if you encounter an issue while upgrading a node. This is a common
knee-jerk reaction which can prove costly because the cluster will
rebalance automatically, adding more time to your upgrade window.
Either fix the problem on the server or replace node using the
"replace_address" flag.
  * Test, test, and test again. Familiarity with the process is your
friend when the unexpected happens.
  * Plan ahead and rehearse your recovery method (i.e. replace the node)
should you run into unexpected issues.
  * Stick to the plan and be prepared to implement it -- don't deviate.
Don't spend 4 hours or more investigating why a server won't start.
  * Be decisive. Activate your recovery/remediation plan immediately.

I'm sure others will chime in with their recommendations. Let us know 
how you go as I'm sure others would be interested in hearing from your 
experience. Not a lot of shops have a deployment as large as yours so 
you are in an enviable position. Good luck!


On Thu, Jan 30, 2020 at 3:45 PM Anshu Vajpayee > wrote:


Hi Team,
What is the best way to patch OS of 1000 nodes Multi DC Cassandra
cluster where we cannot suspend application traffic( we can redirect
traffic to one DC).

Please suggest if anyone has any best practice around it.

-- 
*C*heers,*

*Anshu V*
*
*



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

Re: Cassandra going OOM due to tombstones (heapdump screenshots provided)

[Michael Shuler]

Some environment details like Cassandra version, amount of physical RAM, 
JVM configs (heap and others), and any other non-default cassandra.yaaml 
configs would help. The amount of data, number of keyspaces & tables, 
since you mention "clients", would also be helpful for people to suggest 
tuning improvements.


Michael

On 1/24/20 5:16 AM, Behroz Sikander wrote:

We recently had a lot of OOM in C* and it was generally happening during 
startup.
We took some heap dumps but still cannot pin point the exact reason. So, we 
need some help from experts.

Our clients are not explicitly deleting data but they have TTL enabled.

C* details:

show version

[cqlsh 5.0.1 | Cassandra 2.2.9 | CQL spec 3.3.1 | Native protocol v4]

Most of the heap was allocated was the object[]
- org.apache.cassandra.db.Cell
  
Heap dump images:

Heap usage by class: https://pasteboard.co/IRrfu70.png
Classes using most heap: https://pasteboard.co/IRrgszZ.png
Overall heap usage: https://pasteboard.co/IRrg7t1.png

What could be the reason for such OOM? Something that we can tune to improve 
this?
Any help would be much appreciated.


-
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: COPY command with where condition

[Michael Shuler]

On 1/17/20 9:50 AM, adrien ruffie wrote:

Thank you very much,

  so I do this request with for example -->

./dsbulk unload --dsbulk.schema.keyspace 'dev_keyspace' -query "SELECT * 
FROM probe_sensors WHERE localisation_id = 208812 ALLOW FILTERING" -url 
/home/dump



But I get the following error
com.datastax.dsbulk.executor.api.exception.BulkExecutionException: 
Statement execution failed: SELECT * FROM crt_sensors WHERE site_id = 
208812 ALLOW FILTERING (Cassandra timeout during read query at 
consistency LOCAL_ONE (1 responses were required but only 0 replica 
responded))


but I configured my driver with following driver.conf, but nothing work 
correctly. Do you know what is the problem ?


datastax-java-driver {
     basic {


         contact-points = ["data1com:9042","data2.com:9042"]


typo?

mshuler@hana:~$ echo "QUIT" | nc -w 10 data2.com 9042
data2.com [35.208.148.117] 9042 (?) : Connection timed out



         request {
             timeout = "200"
             consistency = "LOCAL_ONE"

         }
     }
     advanced {

         auth-provider {
             class = PlainTextAuthProvider
             username = "superuser"
             password = "mypass"

         }
     }
}


Kind regards,
Michael

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

Re: Cassandra build failing after Central Repository HTTPS

[Michael Shuler]

I just did a quick `rm -r ~/.m2/repository/` so the build would download 
everything, and with 2.2.14 tag + 63ff65a8dd, the build succeeded for me 
fine, pulling everything from https. Not sure where to go, unless the 
circleci container is somehow contaminated with http cached data.


Michael

On 1/15/20 6:05 PM, Michael Shuler wrote:

Bleh, sorry, you updated those, right.

I don't see any other related commits to build.xml nor 
build.properties.default.. Some elderly sub-dependent that has an http 
URL in it, perhaps?




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

Re: Cassandra build failing after Central Repository HTTPS

[Michael Shuler]

Bleh, sorry, you updated those, right.

I don't see any other related commits to build.xml nor 
build.properties.default.. Some elderly sub-dependent that has an http 
URL in it, perhaps?


--
Michael

On 1/15/20 5:44 PM, Leon Zaruvinsky wrote:

Hey all,

I'm having trouble with the building Cassandra 2.2.14 on CircleCI since 
Central Repo has stopped supporting http.*


* 
https://central.sonatype.org/articles/2020/Jan/15/501-https-required-error/


I've updated the build.properties and build.xml files to use https.  
However, it seems that the ant build starts to use https and then 
switches to http after a few artifacts:



maven-ant-tasks-retrieve-build: [artifact:dependencies] Downloading: 
junit/junit/4.6/junit-4.6.pom from repository central at 
https://repo1.maven.org/maven2 [artifact:dependencies] Transferring 1K 
from central [artifact:dependencies] Downloading: 
org/assertj/assertj-core/3.12.0/assertj-core-3.12.0.pom from repository 
central at https://repo1.maven.org/maven2 [artifact:dependencies] 
Transferring 13K from central [artifact:dependencies] Downloading: 
org/assertj/assertj-parent-pom/2.2.2/assertj-parent-pom-2.2.2.pom from 
repository central at https://repo1.maven.org/maven2 
[artifact:dependencies] Transferring 16K from central 
[artifact:dependencies] Downloading: 
org/junit/junit-bom/5.4.0/junit-bom-5.4.0.pom from repository central at 
http://repo1.maven.org/maven2 [artifact:dependencies] Error transferring 
file: Server returned HTTP response code: 501 for URL: 
http://repo1.maven.org/maven2/org/junit/junit-bom/5.4.0/junit-bom-5.4.0.pom 
[artifact:dependencies] [WARNING] Unable to get resource 
'org.junit:junit-bom:pom:5.4.0' from repository central 
(http://repo1.maven.org/maven2): Error transferring file: Server 
returned HTTP response code: 501 for URL: 
http://repo1.maven.org/maven2/org/junit/junit-bom/5.4.0/junit-bom-5.4.0.pom 
[artifact:dependencies] An error has occurred while processing the Maven 
artifact tasks. [artifact:dependencies] Diagnosis: 
[artifact:dependencies] [artifact:dependencies] Unable to resolve 
artifact: Unable to get dependency information: Unable to read the 
metadata file for artifact 'org.assertj:assertj-core:jar': POM 
'org.junit:junit-bom' not found in repository: Unable to download the 
artifact from any repository [artifact:dependencies] 
[artifact:dependencies] org.junit:junit-bom:pom:5.4.0 
[artifact:dependencies] [artifact:dependencies] from the specified 
remote repositories: [artifact:dependencies] central 
(http://repo1.maven.org/maven2) [artifact:dependencies] 
[artifact:dependencies] for project org.junit:junit-bom 
[artifact:dependencies] org.assertj:assertj-core:jar:3.12.0 
[artifact:dependencies] [artifact:dependencies] from the specified 
remote repositories: [artifact:dependencies] apache 
(https://repo.maven.apache.org/maven2), [artifact:dependencies] central 
(https://repo1.maven.org/maven2) [artifact:dependencies] 
[artifact:dependencies] Path to dependency: [artifact:dependencies] 1) 
org.apache.cassandra:cassandra-build-deps:jar:2.2.14-SNAPSHOT 
[artifact:dependencies] [artifact:dependencies]




There are no references to http://repo1.maven.org/maven2 anywhere in my 
repo.   One theory is that this reference is being automatically 
injected somewhere, but I'm not sure where or how to stop it.


Has anyone else encountered this or has suggestions for how to fix?

Thanks,
Leon


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

Re: Cassandra build failing after Central Repository HTTPS

[Michael Shuler]

You could cherry-pick sha 63ff65a8dd3a31e500ae5ec6232f1f9eade6fa3d which 
was committed after the 2.2.14 release tag.


https://github.com/apache/cassandra/commit/63ff65a8dd3a31e500ae5ec6232f1f9eade6fa3d

--
Kind regards,
Michael

On 1/15/20 5:44 PM, Leon Zaruvinsky wrote:

Hey all,

I'm having trouble with the building Cassandra 2.2.14 on CircleCI since 
Central Repo has stopped supporting http.*


* 
https://central.sonatype.org/articles/2020/Jan/15/501-https-required-error/


I've updated the build.properties and build.xml files to use https.  
However, it seems that the ant build starts to use https and then 
switches to http after a few artifacts:



maven-ant-tasks-retrieve-build: [artifact:dependencies] Downloading: 
junit/junit/4.6/junit-4.6.pom from repository central at 
https://repo1.maven.org/maven2 [artifact:dependencies] Transferring 1K 
from central [artifact:dependencies] Downloading: 
org/assertj/assertj-core/3.12.0/assertj-core-3.12.0.pom from repository 
central at https://repo1.maven.org/maven2 [artifact:dependencies] 
Transferring 13K from central [artifact:dependencies] Downloading: 
org/assertj/assertj-parent-pom/2.2.2/assertj-parent-pom-2.2.2.pom from 
repository central at https://repo1.maven.org/maven2 
[artifact:dependencies] Transferring 16K from central 
[artifact:dependencies] Downloading: 
org/junit/junit-bom/5.4.0/junit-bom-5.4.0.pom from repository central at 
http://repo1.maven.org/maven2 [artifact:dependencies] Error transferring 
file: Server returned HTTP response code: 501 for URL: 
http://repo1.maven.org/maven2/org/junit/junit-bom/5.4.0/junit-bom-5.4.0.pom 
[artifact:dependencies] [WARNING] Unable to get resource 
'org.junit:junit-bom:pom:5.4.0' from repository central 
(http://repo1.maven.org/maven2): Error transferring file: Server 
returned HTTP response code: 501 for URL: 
http://repo1.maven.org/maven2/org/junit/junit-bom/5.4.0/junit-bom-5.4.0.pom 
[artifact:dependencies] An error has occurred while processing the Maven 
artifact tasks. [artifact:dependencies] Diagnosis: 
[artifact:dependencies] [artifact:dependencies] Unable to resolve 
artifact: Unable to get dependency information: Unable to read the 
metadata file for artifact 'org.assertj:assertj-core:jar': POM 
'org.junit:junit-bom' not found in repository: Unable to download the 
artifact from any repository [artifact:dependencies] 
[artifact:dependencies] org.junit:junit-bom:pom:5.4.0 
[artifact:dependencies] [artifact:dependencies] from the specified 
remote repositories: [artifact:dependencies] central 
(http://repo1.maven.org/maven2) [artifact:dependencies] 
[artifact:dependencies] for project org.junit:junit-bom 
[artifact:dependencies] org.assertj:assertj-core:jar:3.12.0 
[artifact:dependencies] [artifact:dependencies] from the specified 
remote repositories: [artifact:dependencies] apache 
(https://repo.maven.apache.org/maven2), [artifact:dependencies] central 
(https://repo1.maven.org/maven2) [artifact:dependencies] 
[artifact:dependencies] Path to dependency: [artifact:dependencies] 1) 
org.apache.cassandra:cassandra-build-deps:jar:2.2.14-SNAPSHOT 
[artifact:dependencies] [artifact:dependencies]




There are no references to http://repo1.maven.org/maven2 anywhere in my 
repo.   One theory is that this reference is being automatically 
injected somewhere, but I'm not sure where or how to stop it.


Has anyone else encountered this or has suggestions for how to fix?

Thanks,
Leon


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

Re: 回复：Re: Reply:Reply: Re:__Why_suddenly_cassandra_3.11.4_and_3.11.3_“can_not_find_or_load_main_class_-ea”?

[Michael Shuler]

Aha.

conf/cassandra-env.sh: for opt in `grep "^-" $JVM_OPTS_FILE`

You might try --color=auto, instead of =always in your shell config. I 
think that may only output the colors when connected to a terminal and 
leave the programmatic JVM_OPTS buildup clean. Cassandra should really 
be run as a non-interactive daemon user with limited privileges, but 
that's a different conversation.


Kind regards,
Michael

On 12/29/19 2:50 AM, gloCalHelp.com wrote:

TO Michael：
      Thank you for your guiding. I check the conf/jvm.options, it is 
not changed .


        Anyway, I find the strange cause now: if I add "export 
GREP_OPTIONS='--color=always' GREP_COLOR='1;33"
not only in /etc/bashrc but also in ~/.bashrc, it will add strange code 
to stop to load cassandra and throw the -ea error.


      Thanks Jeff, Dimo,Shalom and other helps for your help.


Sincerely yours,
Georgelin
www_8ems_...@sina.com
mobile:0086 180 5986 1565


- 原始邮件 -
发件人：Michael Shuler 
收件人：user@cassandra.apache.org
主题：Re: Reply:Reply: 
Re:__Why_suddenly_cassandra_3.11.4_and_3.11.3_“can_not_find_or_load_main_class_-ea”?

日期：2019年12月28日 00点38分

Reading the log, it is apparent that something/someone has edited
conf/jvm.options and it now includes ANSI escape codes. This can be seen
in the log where it builds up JVM_OPTS and the final exec call. If this
same conf/jvm.options file was used to start up the various versions
tested, this also explains why the problem persists.
Actual final error from log using `less` to view:
Error: Could not find or load main class ESC[1;88mESC[K-ESC[mESC[Kea
ESC[1;88m is a console color code, I believe(?).
Fix the edited conf/jvm.options configuration file or start with a fresh
copy, perhaps using a different text editor.
Kind regards,
Michael
On 12/27/19 6:21 AM, gloCalHelp.com wrote:
 > P.S.: Sorry that I don't receive the mail sent last night, so I resend
 > the below mail.
 >
 > TO Jeff：
 >     Thank you very much for your good method to see the shell
 > program's execution log, but the log is long, and
 > even I set CASSANDRA_HOME and JAVA_HOME at the beginning of
 > bin/cassandra, the echo show both them are correct,
 > the the cassandraDaemon.class is really in the detect classpath of
 > $CASSANDRA_HOME/lib/ache-cassandra-3.11.3.jar,
 > it still suddenly failed to start?
 >  And I don't know why finally the -x log display some
 > strange character among the error "Error: Could not find or load main
 > class -ea  " as
 > 
  "Error: Could not find or load main class -ea",

 > why there are some strange character insert?Has hacker change my bash's
 > binary code to insert these strange code? why the hacker prevent me from
 > developing and using cassandra?
 > the bash debug log is as the atachment file of
 > "ShellDebugNoGrepColor3.log" .
 >
 >
 > Sincerely yours,
 > Georgelin
 > www_8ems_...@sina.com
 > mobile:0086 180 5986 1565
 >
 >
 > - 原始邮件 -
 > 发件人：Jeff Jirsa 
 > 收件人：user@cassandra.apache.org
 > 主
 > 
题：Re:__Why_suddenly_cassandra_3.11.4_and_3.11.3_“can_not_find_or_load_main_class_- 


 > ea”?
 > 日期：2019年12月26日 03点36分
 >
 > bin/cassandra sources a few different files and tries to source the
 > right ones but does try some system paths
 >
 > One of those probably has the startup args mangled so the jvm flag to
 > enable assertions isn’t in the right order
 >
 > Sent from my iPhone
 >
 >> On Dec 25, 2019, at 8:06 AM, Dimo Velev  wrote:
 >>
 >> Please add -x to your shebang (the line that starts with #!) - e.g.
 >> #!/bin/bash -x to your Cassandra startup script. This will log each
 >> line before executing it. If that does not point you to the problem
 >> paste the output here.
 >>
 >> If something breaks even for separate checkout, maybe the scripts are
 >> sourcing in something from your user home directory which is broken
 >> (or your shell profile/rc)
 >>
 >>
 >>  Original message 
 >> From: "gloCalHelp.com" 
 >> Date: 24/12/2019 09:39 (GMT+01:00)
 >> To: Dimo Velev 
 >> Cc: user , dev-help
 >> 
 >> Subject: 回
 >> 
复：RE:_Why_suddenly_cassandra_3.11.4_and_3.11.3_“can_not_find_or_load_main_class_- 


 >> ea”?
 >>
 >> To Dimo：
 >>
 >>      Thank you for your reply and guiding , but not only my customized
 >> soure, but also the original cassandra 3.11.3/4 suddenly cann't run as
 >> several years ago and throw the -ea errors, and I have check the
 >> original running bin/cassandra source and centos's environment, no any
 >> -ea let. And the c

Re: Reply:Reply: Re:__Why_suddenly_cassandra_3.11.4_and_3.11.3_“can_not_find_or_load_main_class_-ea”?

[Michael Shuler]

Reading the log, it is apparent that something/someone has edited 
conf/jvm.options and it now includes ANSI escape codes. This can be seen 
in the log where it builds up JVM_OPTS and the final exec call. If this 
same conf/jvm.options file was used to start up the various versions 
tested, this also explains why the problem persists.


Actual final error from log using `less` to view:
Error: Could not find or load main class ESC[1;88mESC[K-ESC[mESC[Kea

ESC[1;88m is a console color code, I believe(?).

Fix the edited conf/jvm.options configuration file or start with a fresh 
copy, perhaps using a different text editor.


Kind regards,
Michael

On 12/27/19 6:21 AM, gloCalHelp.com wrote:
P.S.: Sorry that I don't receive the mail sent last night, so I resend 
the below mail.


TO Jeff：
     Thank you very much for your good method to see the shell 
program's execution log, but the log is long, and
even I set CASSANDRA_HOME and JAVA_HOME at the beginning of 
bin/cassandra, the echo show both them are correct,
the the cassandraDaemon.class is really in the detect classpath of 
$CASSANDRA_HOME/lib/ache-cassandra-3.11.3.jar,

it still suddenly failed to start?
  And I don't know why finally the -x log display some 
strange character among the error "Error: Could not find or load main 
class -ea  " as

  
    "Error: Could not find or load main 
class -ea",
why there are some strange character insert?Has hacker change my bash's 
binary code to insert these strange code? why the hacker prevent me from 
developing and using cassandra?
the bash debug log is as the atachment file of 
"ShellDebugNoGrepColor3.log" .



Sincerely yours,
Georgelin
www_8ems_...@sina.com
mobile:0086 180 5986 1565


- 原始邮件 -
发件人：Jeff Jirsa 
收件人：user@cassandra.apache.org
主 
题：Re:__Why_suddenly_cassandra_3.11.4_and_3.11.3_“can_not_find_or_load_main_class_- 
ea”?

日期：2019年12月26日 03点36分

bin/cassandra sources a few different files and tries to source the 
right ones but does try some system paths


One of those probably has the startup args mangled so the jvm flag to 
enable assertions isn’t in the right order


Sent from my iPhone


On Dec 25, 2019, at 8:06 AM, Dimo Velev  wrote:

Please add -x to your shebang (the line that starts with #!) - e.g. 
#!/bin/bash -x to your Cassandra startup script. This will log each 
line before executing it. If that does not point you to the problem 
paste the output here.


If something breaks even for separate checkout, maybe the scripts are 
sourcing in something from your user home directory which is broken 
(or your shell profile/rc)



 Original message 
From: "gloCalHelp.com" 
Date: 24/12/2019 09:39 (GMT+01:00)
To: Dimo Velev 
Cc: user , dev-help 

Subject: 回 
复：RE:_Why_suddenly_cassandra_3.11.4_and_3.11.3_“can_not_find_or_load_main_class_- 
ea”?


To Dimo：

     Thank you for your reply and guiding , but not only my customized 
soure, but also the original cassandra 3.11.3/4 suddenly cann't run as 
several years ago and throw the -ea errors, and I have check the 
original running bin/cassandra source and centos's environment, no any 
-ea let. And the cassandra's running JVM's parameters are shown as 
below, there
 is no any -ea JVM variable left. I will check Centos JVM's 
environment, in addition to the suddenly deleted lib folder too, it 
seems that some hackers play a prank on me to stop my developing and 
using cassandra.


      Is there any genius can help me?

Sincerely yours,
Georgelin
www_8ems_...@sina.com
mobile:0086 180 5986 1565


- 原始邮件 -
发件人：Dimo Velev 
收件人：user@cassandra.apache.org, dev-help 
, www_8ems_com 
主 
题：RE:_Why_suddenly_cassandra_3.11.4_and_3.11.3_“can_not_find_or_load_main_class_- 
ea”?

日期：2019年12月24日 16点13分

-ea is a jvm parameter to enable assertions. Maybe you are passing it 
at the wrong place and the jvm interprets it as class name that you 
want to start.


 Original message 
From: "gloCalHelp.com" 
Date: 24/12/2019 08:03 (GMT+01:00)
To: user , dev-help 
, www_8ems_com 
Subject: Why suddenly cassandra 3.11.4 and 3.11.3 “can not find or 
load main class -ea”?


Dear cassandra pioneers and users：
Yesterday afternoon, I can run cassandra 3.11.4's git-clone-src by 
using "bin/cassandra", but after I changed some codes by Eclipse,
 and compile without any error, not only the runnable source version, 
but also I redownload 3.11.4-bin.tar.gz and 3.11.3 from official website,
they can't run by command of "./bin/cassandra", the steps and logs are 
as below:


[gloCalHelp.com@gloCalHelp5 apache-cassandra-3.11.4]$ ./bin/cassandra 
& [1] 5872 [gloCalHelp.com@gloCalHelp5 apache-cassandra-3.11.4]$ 
classname is+ org.apache.cassandra.service.CassandraDaemon +CLASSPATH 

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 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

[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 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 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 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

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

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 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 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: 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

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: 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

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: 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]

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

[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

[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 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 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

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

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: 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: 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: 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%2F4bbd28adata=01%7C01
>> %7Cthomas.steinmaurer%40dynatrace.com%7C4b4bcec4c04d4c52f74c08d61
>> fc9e154%7C70ebe3a35b30435d9d677716d74ca190%7C1sdata=YqHz6ul
>> 55SdPuxHhz5qubNb6MeK1XEjxg63Ttf2v6Uc%3Dreserved=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%2Fc0aa79edata=01%7C01%
>> 7Cthomas.steinmaurer%40dynatrace.com%7C4b4bcec4c04d4c52f74c08d61fc
>> 9e154%7C70ebe3a35b30435d9d677716d74ca190%7C1sdata=256fWCvc
>> XDCdFqeQYe618JZfQQDAmV8LVRga4UBvSKs%3Dreserved=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: 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: 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

[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

[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 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

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

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: 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: 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]

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 <mich...@pbandjelly.org
> <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<InetSocketAddress, Throwable> map = e.getErrors();
> >             for(Entry<InetSocketAddress, Throwable> 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)
>

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
> 
> 

Re: How to configure Cassandra to NOT use SSLv2?

[Michael Shuler]

our situation would be 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" <lou.degen...@gmail.com
> <mailto:lou.degen...@gmail.com>>
> *An: *"user" <user@cassandra.apache.org
> <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
> <lou.degen...@gmail.com <mailto:lou.degen...@gmail.com>> wrote:
> 
> 3.0.9
> 
> On Fri, Apr 20, 2018 at 10:26 PM, Michael Shuler
> <mich...@pbandjelly.org <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: 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]

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: [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: 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: 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: 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: 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 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 <mich...@pbandjelly.org
>>> <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/2

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 <mich...@pbandjelly.org
>> <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]

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 <mich...@pbandjelly.org
>>> <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 <cyril.scet...@free.fr
>>>>> <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]

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 <mich...@pbandjelly.org
>> <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 <cyril.scet...@free.fr
>>>> <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]

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: Amazon Time Sync Service + ntpd vs chrony

[Michael Shuler]

As long as your nodes are syncing time using the same method, that
should be good. Don't mix daemons, however, since they may sync from
different sources. Whether you use ntpd, openntp, ntpsec, chrony isn't
really important, since they are all just background daemons to sync the
system clock. There is nothing Cassandra-specific.

-- 
Kind regards,
Michael

On 03/08/2018 04:15 AM, Kyrylo Lebediev wrote:
> Hi!
> 
> Recently Amazon announced launch of Amazon Time Sync Service
> (https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-time-sync-service/)
> and now it's AWS-recommended way for time sync on EC2 instances
> (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html).
> It's stated there that chrony is faster / more precise than ntpd.
> 
> Nothing to say correct time sync configuration is very important for any
> C* setup.
> 
> Does anybody have positive experience using crony, Amazon Time Sync
> Service with Cassandra and/or combination of them?
> Any concerns regarding chrony + Amazon Time Sync Service + Cassandra?
> Are there any chrony best-practices/custom settings for C* setups?
> 
> Thanks,
> Kyrill
> 


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

Re: Jon Haddad on Diagnosing Performance Problems in Production

[Michael Shuler]

On 02/27/2018 10:20 AM, Nicolas Guyomar wrote:
> Is Jon blog
> post 
> https://academy.datastax.com/planet-cassandra/blog/cassandra-summit-recap-diagnosing-problems-in-production
> was relocated somewhere ?

https://web.archive.org/web/20160322011022/planetcassandra.org/blog/cassandra-summit-recap-diagnosing-problems-in-production

-- 
Kind regards,
Michael

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

Re: Missing 3.11.X cassandra debian packages

[Michael Shuler]

On 02/21/2018 11:56 AM, Zachary Marois wrote:
> Starting in that last two weeks (I successfully installed cassandra
> sometime in the last two weeks), I'm guessing on 2/19 when version
> 3.11.2 was released, the cassandra apt package version 3.11.1 became
> unstable. It doesn't seem to be published in the
> http://www.apache.org/dist/cassandra/debian repository anymore (at least
> not in a valid state).
> 
> 
> Despite the package actually being in the repository still
> 
> http://www.apache.org/dist/cassandra/debian/pool/main/c/cassandra/cassandra_3.11.1_all.deb
>  
> 
> It is no longer in the Packages list

This is just the way reprepro works - only the latest version will be
reported.

This is a feature. Users really should be installing the latest release
version.

> http://dl.bintray.com/apache/cassandra/dists/311x/main/binary-amd64/Packages 
> 
> It looks like version 3.11.2 was released on 2/19.
> 
> I'm guessing that publishing dropped the 3.11.1 version from the
> packages list.

This happens for every release. Every so often, branches will be culled
from http://www.apache.org/dist/, when they are no longer supported, so
periodically, complete series of packages will disappear. However, they
will always be available from the canonical Apache release repository.

The canonical release repository for Apache projects is
archive.apache.org. Every release artifact of the Apache Cassandra
project appears at:

  http://archive.apache.org/dist/cassandra/

A debian package user that cannot upgrade to the latest version via
apt-get can always use, for example wget to fetch .deb. files they need
from the repo pool dir:

  http://archive.apache.org/dist/cassandra/debian/pool/main/c/cassandra/

You will not find Cassandra 0.7.9 in the "current" apt repositories any
longer, since they are unsupported, but there are indeed people using
that version. The above spot is where to find the .deb packages for
0.7.9, and all older releases.

-- 
Warm regards,
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.2 released - PLEASE READ NOTICE

[Michael Shuler]

PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092)
--

The maximum expiration timestamp that can be represented by the storage
engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL
thatl expire after this date are not currently supported. By default,
INSERTS with TTL exceeding the maximum supported date are rejected, but
it's possible to choose a different expiration overflow policy. See
CASSANDRA-14092.txt for more details.

Prior to 3.0.16 (3.0.X) and 3.11.2 (3.11.x) there was no protection
against INSERTS with TTL expiring after the maximum supported date,
causing the expiration time field to overflow and the records to expire
immediately. Clusters in the 2.X and lower series are not subject to
this when assertions are enabled. Backed up SSTables can be potentially
recovered and recovery instructions can be found on the
CASSANDRA-14092.txt file.

If you use or plan to use very large TTLS (10 to 20 years), read
CASSANDRA-14092.txt for more information.
--

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

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://goo.gl/mQjYnb
[2]: (NEWS.txt) https://goo.gl/NJGdhu
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

[RELEASE] Apache Cassandra 3.0.16 released - PLEASE READ NOTICE

[Michael Shuler]

PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092)
--

The maximum expiration timestamp that can be represented by the storage
engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL
thatl expire after this date are not currently supported. By default,
INSERTS with TTL exceeding the maximum supported date are rejected, but
it's possible to choose a different expiration overflow policy. See
CASSANDRA-14092.txt for more details.

Prior to 3.0.16 (3.0.X) and 3.11.2 (3.11.x) there was no protection
against INSERTS with TTL expiring after the maximum supported date,
causing the expiration time field to overflow and the records to expire
immediately. Clusters in the 2.X and lower series are not subject to
this when assertions are enabled. Backed up SSTables can be potentially
recovered and recovery instructions can be found on the
CASSANDRA-14092.txt file.

If you use or plan to use very large TTLS (10 to 20 years), read
CASSANDRA-14092.txt for more information.
--

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.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 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/ST7ij6
[2]: (NEWS.txt) https://goo.gl/Ek5hve
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

[RELEASE] Apache Cassandra 2.2.12 released - PLEASE READ NOTICE

[Michael Shuler]

PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092)
--

The maximum expiration timestamp that can be represented by the storage
engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL
thatl expire after this date are not currently supported. By default,
INSERTS with TTL exceeding the maximum supported date are rejected, but
it's possible to choose a different expiration overflow policy. See
CASSANDRA-14092.txt for more details.

Prior to 3.0.16 (3.0.X) and 3.11.2 (3.11.x) there was no protection
against INSERTS with TTL expiring after the maximum supported date,
causing the expiration time field to overflow and the records to expire
immediately. Clusters in the 2.X and lower series are not subject to
this when assertions are enabled. Backed up SSTables can be potentially
recovered and recovery instructions can be found on the
CASSANDRA-14092.txt file.

If you use or plan to use very large TTLS (10 to 20 years), read
CASSANDRA-14092.txt for more information.
--

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.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 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/a6L1TE
[2]: (NEWS.txt) https://goo.gl/M9jhdZ
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

[RELEASE] Apache Cassandra 2.1.20 released - PLEASE READ NOTICE

[Michael Shuler]

PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092)
--

The maximum expiration timestamp that can be represented by the storage
engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL
thatl expire after this date are not currently supported. By default,
INSERTS with TTL exceeding the maximum supported date are rejected, but
it's possible to choose a different expiration overflow policy. See
CASSANDRA-14092.txt for more details.

Prior to 3.0.16 (3.0.X) and 3.11.2 (3.11.x) there was no protection
against INSERTS with TTL expiring after the maximum supported date,
causing the expiration time field to overflow and the records to expire
immediately. Clusters in the 2.X and lower series are not subject to
this when assertions are enabled. Backed up SSTables can be potentially
recovered and recovery instructions can be found on the
CASSANDRA-14092.txt file.

If you use or plan to use very large TTLS (10 to 20 years), read
CASSANDRA-14092.txt for more information.
--

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

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/5M7w4X
[2]: (NEWS.txt) https://goo.gl/Kd2kF3
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

Re: Cassandra is not running

[Michael Shuler]

On 02/13/2018 09:45 AM, Jürgen Albersdorfer wrote:
> 1.8.0_161 is not yet supported - try 1.8.0_151
> 
>> Am 13.02.2018 um 16:44 schrieb Irtiza Ali > >:
>>
>> 1.8.0_161
> 

Or install the 3.11.2 tentative release, which should work fine on
1.8.0_161.

https://lists.apache.org/thread.html/6c38262e25cfca27b4e697aa429fe1c51cb83b8fa341ec8a860c272b@%3Cdev.cassandra.apache.org%3E

Looks like a packaged install, so you can find those at:
https://people.apache.org/~mshuler/

-- 
Kind regards,
Michael

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

Releases 2.1.20, 2.2.12, 3.0.16, & 3.11.2 are now up for vote by the PMC

[Michael Shuler]

Tentative tags have been pushed and releases 2.1.20, 2.2.12, 3.0.16, &
3.11.2 are now up for vote by the PMC to address CASSANDRA-14092, as
well as all the other fixes/features committed to the respective branches.

If you would like the links to the tentative release artifacts/packages
and possibly have time to test, you can find those links in the VOTE
messages: https://lists.apache.org/list.html?d...@cassandra.apache.org

-- 
Warm regards,
Michael



signature.asc
Description: OpenPGP digital signature

Re: node restart causes application latency

[Michael Shuler]

On 02/06/2018 12:58 PM, Mike Torra wrote:
> 
> I restart a node like this:
> 
> nodetool disablethrift && nodetool disablegossip && nodetool drain
> sudo service cassandra restart

Just a guess here - are you really only using thrift?
(ie. `nodetool disablebinary`)

> When I do that, I very often get timeouts and errors like this in my
> nodejs app:
> 
> Error: Cannot achieve consistency level LOCAL_ONE

Which nodejs driver? Is it a "gossip-aware" driver and getting
notifications of client port shutdown on the nodes? Verbose logging at
the clients while going through a restart may be helpful to see what's
going on.

> I've tried waiting between steps of shutting down cassandra, and I've
> tried stopping, waiting, then starting the node. One thing I've noticed
> is that even after `nodetool drain`ing the node, there are open
> connections to other nodes in the cluster (ie looking at the output of
> netstat) until I stop cassandra. I don't see any errors or warnings in
> the logs.

What port are the connections on? 9160 (thrift) or 9042 (native)?

-- 
Kind regards,
Michael

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

Re: Security Updates

[Michael Shuler]

I should also mention the dev@ mailing list - this is where the [VOTE]
emails are sent and you'd get an advanced heads up on upcoming releases,
along with the release emails that are sent to both user@ and dev@. The
dev@ traffic is generally lower than user@, so pretty easy to spot votes
& releases.

-- 
Michael

On 01/31/2018 01:12 PM, Michael Shuler wrote:
> I usually install cron-apt for Ubuntu & Debian, forward and read root's
> email to be notified of all system upgrades, including Cassandra.
> 
> There are likely other utilities for other operating systems, or just a
> cron script that checks for system update & emails would work, too.
> 
> Also, it's possible to use something like urlwatch to look for changes
> on http://cassandra.apache.org/download/ or any site, email out a
> notification, etc. Maybe http://fetchrss.com/ or similar would work?
> 
> I think there are a multitude of immediate ways to do this, until there
> is a site patch submitted to JIRA for RSS addition.
> 


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

Re: Security Updates

[Michael Shuler]

I usually install cron-apt for Ubuntu & Debian, forward and read root's
email to be notified of all system upgrades, including Cassandra.

There are likely other utilities for other operating systems, or just a
cron script that checks for system update & emails would work, too.

Also, it's possible to use something like urlwatch to look for changes
on http://cassandra.apache.org/download/ or any site, email out a
notification, etc. Maybe http://fetchrss.com/ or similar would work?

I think there are a multitude of immediate ways to do this, until there
is a site patch submitted to JIRA for RSS addition.

-- 
Michael

On 01/31/2018 12:22 PM, Rob Oxspring wrote:
> Hi,
> 
> As a user of Cassandra I'd like to be able to get notified when there are 
> security releases so that I can get my installation patched ASAP. For feature 
> and patch releases I'm happy to come and look at the web page or trawl 
> through some mail archives, but I'd like for security releases to come and 
> find me.
> 
> Is there a dedicated mailing list for this?
> Or a dedicated list for just announcements without everyday chatter?
> An RSS / atom feed would work just as well.
> 
> Thanks,
> 
> Rob Oxspring
> 
> -
> 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: AbstractMethodError from JMXServerUtils after update from Java 1.8.0_112 to 1.8.0_162

[Michael Shuler]

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

On 01/18/2018 03:29 PM, Stephen Rosenthal wrote:
> Hi,
> 
>  
> 
> I got the following error after updating my Cassandra system from Java
> 1.8.0_112 to 1.8.0_162:
> 
>  
> 
> java.lang.AbstractMethodError:
> org.apache.cassandra.utils.JMXServerUtils$Exporter.exportObject(Ljava/rmi/Remote;ILjava/rmi/server/RMIClientSocketFactory;Ljava/rmi/server/RMIServerSocketFactory;Lsun/misc/ObjectInputFilter;)Ljava/rmi/Remote;
> 
>  
> 
> I did the usual Googling and here’s what I’ve concluded:
> 
>   * Between Java 1.8.0_152 and 1.8.0_162, the interface
> com.sun.jmx.remote.internal.RMIExporter was changed to add a 5^th
> argument to the exportObject method. The class in a Sun “internal”
> package so it probably wasn’t intended for use outside of the JDK.
>   * Cassandra references RMIExporter in
> org.apache.cassandra.utils.JMXServerUtils but uses only 4 arguments
> in the exportObject method:
> 
> https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/utils/JMXServerUtils.java
>   * I was running on Cassandra 3.11 but I also tried 3.11.1 and the
> problem remained.
> 
>  
> 
> I couldn’t find anyone else reporting this bug so I must be doing
> something different. Have others seen this bug? Or is it something
> obvious, i.e. does Cassandra not support running on Java 1.8.0_162 yet?
> 
>  
> 
> Thanks!
> 
> Stephen
> 


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

Re: Upgrade to 3.11.1 give SSLv2Hello is disabled error

[Michael Shuler]

This looks like the post-POODLE commit:
https://issues.apache.org/jira/browse/CASSANDRA-10508

I think you might just set 'TLS' as in the example to use the JVM's
preferred TLS protocol version.

-- 
Michael

On 01/16/2018 08:13 AM, Tommy Stendahl wrote:
> Hi,
> 
> I have problems upgrading a cluster from 3.0.14 to 3.11.1 but when I
> upgrade the first node it fails to gossip.
> 
> I have server encryption enabled on all nodes with this setting:
> 
> server_encryption_options:
>     internode_encryption: all
>     keystore: /usr/share/cassandra/.ssl/server/keystore.jks
>     keystore_password: 'x'
>     truststore: /usr/share/cassandra/.ssl/server/truststore.jks
>     truststore_password: 'x'
>     protocol: TLSv1.2
>     cipher_suites:
> [TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA]
> 
> 
> I get this error in the log:
> 
> 2018-01-16T14:41:19.671+0100 ERROR [ACCEPT-/10.61.204.16]
> MessagingService.java:1329 SSL handshake error for inbound connection
> from 30f93bf4[SSL_NULL_WITH_NULL_NULL:
> Socket[addr=/x.x.x.x,port=40583,localport=7001]]
> javax.net.ssl.SSLHandshakeException: SSLv2Hello is disabled
>     at
> sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:637)
> ~[na:1.8.0_152]
>     at sun.security.ssl.InputRecord.read(InputRecord.java:527)
> ~[na:1.8.0_152]
>     at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983)
> ~[na:1.8.0_152]
>     at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
> ~[na:1.8.0_152]
>     at
> sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:938)
> ~[na:1.8.0_152]
>     at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
> ~[na:1.8.0_152]
>     at sun.security.ssl.AppInputStream.read(AppInputStream.java:71)
> ~[na:1.8.0_152]
>     at java.io.DataInputStream.readInt(DataInputStream.java:387)
> ~[na:1.8.0_152]
>     at
> org.apache.cassandra.net.MessagingService$SocketThread.run(MessagingService.java:1303)
> ~[apache-cassandra-3.11.1.jar:3.11.1]
> 
> I suspect that this has something to do with the change in
> CASSANDRA-10508. Any suggestions on how to get around this would be very
> much appreciated.
> 
> Thanks, /Tommy
> 
> 
> 
> -
> 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: Policy on 3.11.0 packages...

[Michael Shuler]

Old packages are always in the deb repo pool, but reprepro-built
metadata lists only the latest with apt. `wget` and `dpkg` are your
friends here. RPM should "just work" for old packages, I think.

3.11.0 is still fetchable and installable:
(bintray redirect on deb repo)
http://www.apache.org/dist/cassandra/debian/pool/main/c/cassandra/
http://www.apache.org/dist/cassandra/redhat/311x/

Full release archives for every release ever - drill down under debian
and redhat directories:
http://archive.apache.org/dist/cassandra/

-- 
Kind regards,
Michael

On 12/06/2017 11:33 AM, Russell Bateman wrote:
> We maintain a custom-index plug-in that we haven't ported to 3.11.1
> which is a non-zero effort. (Stratio's Lucene plug-in is in the same
> boat here.)
> 
> I would like to inquire as to the non-availability of Debian and RPM
> packages for Cassandra 3.11.0 now that 3.11.1 is the latest. What's the
> thinking on this? Why does package support move on so quickly without
> back-support for most recent, stable version, etc?
> 
> Thanks,
> 
> Russ


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

Re: Running Cassandra on FreeBSD

[Michael Shuler]

Looks simlar to:
https://lists.freebsd.org/pipermail/freebsd-stable/2014-October/080834.html

That ML post was linked on:
https://issues.apache.org/jira/browse/CASSANDRA-8325

That JIRA has a couple patches you might look at for examples.

-- 
Kind regards,
Michael


On 11/17/2017 04:06 AM, Jens Grassel wrote:
> Hi,
> 
> we downloaded the latest release and tried to run it on a FreeBSD 11
> machine which resultet in a JVM crash. Here is the output:
> 
> <---snip--->
> ./bin/cassandra -f  ? 134 
> CompilerOracle: dontinline 
> org/apache/cassandra/db/Columns$Serializer.deserializeLargeSubset 
> (Lorg/apache/cassandra/io/util/DataInputPlus;Lorg/apache/cassandra/db/Columns;I)Lorg/apache/cassandra/db/Columns;
> CompilerOracle: dontinline 
> org/apache/cassandra/db/Columns$Serializer.serializeLargeSubset 
> (Ljava/util/Collection;ILorg/apache/cassandra/db/Columns;ILorg/apache/cassandra/io/util/DataOutputPlus;)V
> CompilerOracle: dontinline 
> org/apache/cassandra/db/Columns$Serializer.serializeLargeSubsetSize 
> (Ljava/util/Collection;ILorg/apache/cassandra/db/Columns;I)I
> CompilerOracle: dontinline 
> org/apache/cassandra/db/commitlog/AbstractCommitLogSegmentManager.advanceAllocatingFrom
>  (Lorg/apache/cassandra/db/commitlog/CommitLogSegment;)V
> CompilerOracle: dontinline 
> org/apache/cassandra/db/transform/BaseIterator.tryGetMoreContents ()Z
> CompilerOracle: dontinline 
> org/apache/cassandra/db/transform/StoppingTransformation.stop ()V
> CompilerOracle: dontinline 
> org/apache/cassandra/db/transform/StoppingTransformation.stopInPartition ()V
> CompilerOracle: dontinline 
> org/apache/cassandra/io/util/BufferedDataOutputStreamPlus.doFlush (I)V
> CompilerOracle: dontinline 
> org/apache/cassandra/io/util/BufferedDataOutputStreamPlus.writeExcessSlow ()V
> CompilerOracle: dontinline 
> org/apache/cassandra/io/util/BufferedDataOutputStreamPlus.writeSlow (JI)V
> CompilerOracle: dontinline 
> org/apache/cassandra/io/util/RebufferingInputStream.readPrimitiveSlowly (I)J
> CompilerOracle: inline 
> org/apache/cassandra/db/rows/UnfilteredSerializer.serializeRowBody 
> (Lorg/apache/cassandra/db/rows/Row;ILorg/apache/cassandra/db/SerializationHeader;Lorg/apache/cassandra/io/util/DataOutputPlus;)V
> CompilerOracle: inline org/apache/cassandra/io/util/Memory.checkBounds (JJ)V
> CompilerOracle: inline org/apache/cassandra/io/util/SafeMemory.checkBounds 
> (JJ)V
> CompilerOracle: inline 
> org/apache/cassandra/utils/AsymmetricOrdering.selectBoundary 
> (Lorg/apache/cassandra/utils/AsymmetricOrdering/Op;II)I
> CompilerOracle: inline 
> org/apache/cassandra/utils/AsymmetricOrdering.strictnessOfLessThan 
> (Lorg/apache/cassandra/utils/AsymmetricOrdering/Op;)I
> CompilerOracle: inline org/apache/cassandra/utils/BloomFilter.indexes 
> (Lorg/apache/cassandra/utils/IFilter/FilterKey;)[J
> CompilerOracle: inline org/apache/cassandra/utils/BloomFilter.setIndexes 
> (JJIJ[J)V
> CompilerOracle: inline org/apache/cassandra/utils/ByteBufferUtil.compare 
> (Ljava/nio/ByteBuffer;[B)I
> CompilerOracle: inline org/apache/cassandra/utils/ByteBufferUtil.compare 
> ([BLjava/nio/ByteBuffer;)I
> CompilerOracle: inline 
> org/apache/cassandra/utils/ByteBufferUtil.compareUnsigned 
> (Ljava/nio/ByteBuffer;Ljava/nio/ByteBuffer;)I
> CompilerOracle: inline 
> org/apache/cassandra/utils/FastByteOperations$UnsafeOperations.compareTo 
> (Ljava/lang/Object;JILjava/lang/Object;JI)I
> CompilerOracle: inline 
> org/apache/cassandra/utils/FastByteOperations$UnsafeOperations.compareTo 
> (Ljava/lang/Object;JILjava/nio/ByteBuffer;)I
> CompilerOracle: inline 
> org/apache/cassandra/utils/FastByteOperations$UnsafeOperations.compareTo 
> (Ljava/nio/ByteBuffer;Ljava/nio/ByteBuffer;)I
> CompilerOracle: inline org/apache/cassandra/utils/vint/VIntCoding.encodeVInt 
> (JI)[B
> INFO  [main] 2017-11-17 11:03:12,020 YamlConfigurationLoader.java:89 - 
> Configuration location: 
> file:/usr/home/jens/apache-cassandra-3.11.1/conf/cassandra.yaml
> INFO  [main] 2017-11-17 11:03:12,366 Config.java:481 - Node 
> configuration:[allocate_tokens_for_keyspace=null; 
> authenticator=AllowAllAuthenticator; authorizer=AllowAllAuthorizer; 
> auto_bootstrap=true; auto_snapshot=true; back_pressure_enabled=false; 
> back_pressure_strategy=org.apache.cassandra.net.RateBasedBackPressure{high_ratio=0.9,
>  factor=5, flow=FAST}; batch_size_fail_threshold_in_kb=50; 
> batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024; 
> broadcast_address=null; broadcast_rpc_address=null; 
> buffer_pool_use_heap_if_exhausted=true; cas_contention_timeout_in_ms=1000; 
> cdc_enabled=false; cdc_free_space_check_interval_ms=250; 
> cdc_raw_directory=null; cdc_total_space_in_mb=0; 
> client_encryption_options=; cluster_name=Test Cluster; 
> column_index_cache_size_in_kb=2; column_index_size_in_kb=64; 
> commit_failure_policy=stop; commitlog_compression=null; 
> commitlog_directory=null; commitlog_max_compression_buffers_in_pool=3; 
> 

Re: UTF8 error

[Michael Shuler]

On 10/18/2017 09:02 PM, Suresh Babu Mallampati wrote:
> cqlsh: Connection error: ('Unable to connect to any servers',
> {'127.0.0.1': UnicodeDecodeError('utf8', '\x00\x00\x00\xf0\x8f\x0e', 3,
> 5, 'unexpected end of data')})

This does appear to be invalid UTF-8, so the error is valid. Perhaps you
could provide a method to reproduce, or you could just clean up that
data if you know the primary key(s)?

Python agrees:
>>> print('\x00\x00\x00\xf0\x8f\x0e'.decode('utf-8'))
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 3-4:
unexpected end of data

From:
https://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder


Decoder output:

Byte number 1 is decimal 0, hex 0x00, octal \000, binary 

U+  
= NULL


Byte number 2 is decimal 0, hex 0x00, octal \000, binary 

U+  
= NULL


Byte number 3 is decimal 0, hex 0x00, octal \000, binary 

U+  
= NULL


Byte number 4 is decimal 240, hex 0xF0, octal \360, binary 
This is the first byte of a 4 byte sequence.

Byte number 5 is decimal 143, hex 0x8F, octal \217, binary 1000
This is continuation byte 1, expecting 2 more.

Byte number 6 is decimal 14, hex 0x0E, octal \016, binary 1110
Previous UTF-8 multibyte sequence incomplete, earlier bytes dropped.

U+000E  
= SHIFT OUT
* known as LOCKING-SHIFT ONE in 8-bit environments


-- 
Kind regards,
Michael

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

Re: [RELEASE] Apache Cassandra 3.11.1 released

[Michael Shuler]

On 10/11/2017 08:33 AM, Lucas Benevides wrote:
> Hello Michael Schuler,
> 
> When will this version become available for upgrade from apt-get? I
> visited the address http://www.apache.org/dist/cassandra/debian and
> there was no version 3111. 
> 
> To me it is easier to upgrade the nodes this way as I am in a lab, not
> in a production site.

The release announcement don't go out until the uploads are all
complete, but it's possible mirrors may be slow. I do check apt before
announcing and 3.11.1 is available for installation.

mshuler@hana:~$ grep 311x /etc/apt/sources.list
deb http://www.apache.org/dist/cassandra/debian 311x main

mshuler@hana:~$ apt-cache policy cassandra
cassandra:
  Installed: (none)
  Candidate: 3.11.1
  Version table:
 3.11.1 0
500 http://www.apache.org/dist/cassandra/debian/ 311x/main amd64
Packages

-- 
Kind regards,
Michael *Shuler*

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

[RELEASE] Apache Cassandra 3.11.1 released

[Michael Shuler]

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

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://goo.gl/QFBuPn
[2]: (NEWS.txt) https://goo.gl/vHd41x
[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.15 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.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 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/knZzCC
[2]: (NEWS.txt) https://goo.gl/HgTN9S
[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.11 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.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 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/QcJrD8
[2]: (NEWS.txt) https://goo.gl/abKrHt
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

[RELEASE] Apache Cassandra 2.1.19 released

[Michael Shuler]

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.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 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/EfNTLV
[2]: (NEWS.txt) https://goo.gl/MYajtt
[3]: https://issues.apache.org/jira/browse/CASSANDRA



signature.asc
Description: OpenPGP digital signature

Re: How do I install Cassandra on AWS

[Michael Shuler]

How to EC2:

  https://aws.amazon.com/ec2/getting-started/

After "Step 4: Connect to your instance", then install Cassandra as in
the steps on the download page.

If you're looking for details on instance configuration and cluster
strategy, a quick search of "ec2 cassandra" found me the AWS whitepaper
with guidelines and best practices:

  https://d0.awsstatic.com/whitepapers/Cassandra_on_AWS.pdf

You might get better help if you provide some specific step you
performed, what you expected to happen, an error you got, what you tried
to fix it, etc.

-- 
Michael

On 10/03/2017 06:28 AM, Lutaya Shafiq Holmes wrote:
>  How do I install Cassandra on AWS- Amazon web services
> 
> The instructions are not listed there
> 
> On 10/2/17, Michael Shuler <mich...@pbandjelly.org> wrote:
>> On 10/02/2017 10:53 AM, Lutaya Shafiq Holmes wrote:
>>>
>>> How do I install Cassandra on AWS- Amazon web services
>>
>> Follow the installation instructions on the following page, relevant to
>> your OS of choice:
>>
>>   http://cassandra.apache.org/download/
>>
>> Let the list know if you have any problems!
>>
>> --
>> Kind regards,
>> Michael
>>
>> -
>> 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: How do I install Cassandra on AWS

[Michael Shuler]

On 10/02/2017 10:53 AM, Lutaya Shafiq Holmes wrote:
> 
> How do I install Cassandra on AWS- Amazon web services

Follow the installation instructions on the following page, relevant to
your OS of choice:

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

Let the list know if you have any problems!

-- 
Kind regards,
Michael

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

Re: Issue with New Production Cluster

[Michael Shuler]

"Connection reset by peer" is almost certainly network issues. Same error:

https://github.com/netty/netty/issues/5993

mtr - ping/trace tool to find possible flaky switch/router
tcpdump and/or wireshark - tools to gather and observe network packets

-- 
Michael

On 09/29/2017 10:38 AM, Thakrar, Jayesh wrote:
> Other things you can do to test network issues (as a non-sysadmin user)
> is to use the following commands -
> 
>  
> 
> "netstat -i"
> 
> This will show all the network interfaces (including any bonded
> interfaces) and the in/out traffic (as rx/tx) and any errors in them.
> 
> Note that these are cumulative counters, so you need to do a number of
> samplings to ensure that the errors, if any, are not old ones.
> 
>  
> 
> "netstat -s"
> 
> This show more extended network level stats - and the info varies by the
> OS flavor and version.
> 
> But many of the stats are kind of self-explanatory.
> 
>  
> 
> *From: *Jeff Jirsa 
> *Date: *Friday, September 29, 2017 at 10:32 AM
> *To: *cassandra 
> *Subject: *Re: Issue with New Production Cluster
> 
>  
> 
> I don't know what logging is available driver side, I'd probably be
> writing a shell script to ping all three servers to see if I can prove
> there's a network problem outside of cassandra first.
> 
>  
> 
> On Fri, Sep 29, 2017 at 8:19 AM, Jonathan Baynes
> > wrote:
> 
> Thank you Jeff, you are a credit to this community.. very helpful
> 
>  
> 
> Last question Is there any logging I can turn on (especially with
> the cassandra drive 2.5.0) that would assist in gaining more of an
> insight as to what’s going on? If I’m getting any failed connections
> at the cassandra layer?
> 
>  
> 
> Thanks
> 
> J
> 
>  
> 
> *From:*Jeff Jirsa [mailto:jji...@gmail.com ]
> *Sent:* 29 September 2017 16:07
> 
> 
> *To:* cassandra
> *Subject:* Re: Issue with New Production Cluster
> 
>  
> 
> The failure detector is seeing updates every 2.1-2.5  seconds, which
> it will ignore because it's over the 2 second default failure
> detector interval.
> 
>  
> 
> If there's no load, there's no reason it shouldn't be seeing it far
> more frequently.
> 
>  
> 
> If you're not seeing any signs of GC pauses (like GCInspector log
> lines), then it seems like you've got a network interface flapping -
> maybe STP is triggering on a port, or a bad cable/interface, or
> something along those lines. 
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> On Fri, Sep 29, 2017 at 7:32 AM, Jonathan Baynes
> >
> wrote:
> 
> Hi Jeff,
> 
>  
> 
> This is version 3.0.11. Being run on Oracle Red Hat Linux.
> 
>  
> 
> If I retry immediately it fails, leave it for 20 minutes, like I
> have just now and retry it and it has worked. (?!?!)
> 
> Ive checked all the logs (system and Debug ) and in the logs I have
> this:
> 
>  
> 
> DEBUG [GossipStage:1] 2017-09-29 15:28:04,390
> FailureDetector.java:456 - Ignoring interval time of 2102011879
>  for /10.172.181.62
> 
> 
> 
> INFO  [SharedPool-Worker-1] 2017-09-29 15:28:07,382 Message.java:615
> - Unexpected exception during request; channel = [id: 0x963c334d,
> L:/10.172.117.61:9042
> 
> 
> - R:/10.172.117.21:51853
> 
> ]
> 
> io.netty.channel.unix.Errors$NativeIoException: syscall:read(...)()
> failed: Connection reset by peerat
> io.netty.channel.unix.FileDescriptor.readAddress(...)(Unknown
> Source) ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> 
> DEBUG [GossipStage:1] 2017-09-29 15:28:07,389
> FailureDetector.java:456 - Ignoring interval time of 2085147992
>  for /10.172.117.63
> 
>