When testing T195741, we discovered that the recently built cassandra 2.2.6-wmf4 has an issue with cqlsh not working out of the box. We are running into CASSANDRA-11850.
workaround:
installing the python-cassandra package, then using CQLSH_NO_BUNDLED=TRUE cqlsh to connect
@Eevans any cahnce we could backport the fix to our version? Or should we just upgrade to 2.2.12?
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| maps: upgrade to cassandra-2.2.6-wmf5 | operations/puppet | production | +1 -1 |
My personal preference would be to apply the patch if it is trivial/small rather than upgrading cassandra.
OK, I've pushed 2.2.6-wmf5 to http://people.wikimedia.org/~eevans (signed with key ID 8D77295D).
It [[ https://github.com/wikimedia/cassandra/compare/wmf/2.2.6-wmf4...wmf/2.2.6-wmf5 | patches the cqlsh shell wrapper to export CQLSH_NO_BUNDLED, and adds python-cassandra as a package dependency ]]. Like -wmf4, this should work on both jessie and stretch, but please test in your respective environments to be sure.
Change 439905 had a related patch set uploaded (by Gehel; owner: Gehel):
[operations/puppet@production] maps: upgrade to cassandra-2.2.6-wmf5
Change 439905 merged by Gehel:
[operations/puppet@production] maps: upgrade to cassandra-2.2.6-wmf5
I think it makes sense to ping @elukey first, yeah, but AQS is pinned to 2.2.6-wmf3, so updating the APT repo should be Safe™ (it would only make it a more difficult to re-provision).
Yep I think that uploading the new version (cassandra-2.2.6-wmf5) to the cassandra22 component should be safe for AQS. Opened https://phabricator.wikimedia.org/T197062 to track the work :)
Seems to work fine in labs, I am ok with uploading it to reprepro (cassandra22 component) for jessie/stretch wikimedia. After that I'll upgrade AQS!