[
https://issues.apache.org/jira/browse/CASSANDRA-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145967#comment-16145967
]
Nathaniel Tabernero edited comment on CASSANDRA-13433 at 8/29/17 7:40 PM:
--------------------------------------------------------------------------
I've attached a patch file against cassandra-3.9 for creating a rpm which works
on Centos 6 ([^cassandra-3.9-centos6.patch]). At the time we upgraded
Cassandra, version 3.9 was the latest stable version. This patch file includes
a rpm spec file which has a dependency on python27 from the centos-release-scl
repo. The python27 package will install python into an alternate location which
will not conflict the Centos 6's default installed python 2.6 . Additionally,
the spec file will modify the cqlsh script to use python 2.7.
Here are the steps we use to install Cassandra 3.9 on Centos 6.9 in our
environment:
{panel}
#Install Java 8, then
sudo yum install centos-release-scl # install SCL repo
sudo yum localinstall cassandra-3.9-2.scl.el6.noarch.rpm #install custom build
cassandra 3.9 rpm
sudo service cassandra start
sudo chkconfig cassandra on
{panel}
If this custom rpm is not available and cassandra 3.9 is already installed
through other means, then:
{panel}
sudo yum install centos-release-scl # install SCL repo
sudo yum install python27 # install Python 2.7
{panel}
Then, manually modify the cqlsh script. Add the following lines after the
comment header
{panel}
\# Enable python2.7 from centos 6 SCL
source /opt/rh/python27/enable
{panel}
I hope this is helpful!
was (Author: ntabernero):
I've attached a patch file against cassandra-3.9 for creating a rpm which works
on Centos 6. At the time we upgraded Cassandra, version 3.9 was the latest
stable version. This patch file includes a rpm spec file which has a dependency
on python27 from the centos-release-scl repo. The python27 package will install
python into an alternate location which will not conflict the Centos 6's
default installed python 2.6 . Additionally, the spec file will modify the
cqlsh script to use python 2.7.
Here are the steps we use to install Cassandra 3.9 on Centos 6.9 in our
environment:
{panel}
#Install Java 8, then
sudo yum install centos-release-scl # install SCL repo
sudo yum localinstall cassandra-3.9-2.scl.el6.noarch.rpm #install custom build
cassandra 3.9 rpm
sudo service cassandra start
sudo chkconfig cassandra on
{panel}
If this custom rpm is not available and cassandra 3.9 is already installed
through other means, then:
{panel}
sudo yum install centos-release-scl # install SCL repo
sudo yum install python27 # install Python 2.7
{panel}
Then, manually modify the cqlsh script. Add the following lines after the
comment header
{panel}
\# Enable python2.7 from centos 6 SCL
source /opt/rh/python27/enable
{panel}
I hope this is helpful!
> RPM distribution improvements and known issues
> ----------------------------------------------
>
> Key: CASSANDRA-13433
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13433
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Attachments: cassandra-3.9-centos6.patch
>
>
> Starting with CASSANDRA-13252, new releases will be provided as both official
> RPM and Debian packages. While the Debian packages are already well
> established with our user base, the RPMs just have been release for the first
> time and still require some attention.
> Feel free to discuss RPM related issues in this ticket and open a sub-task to
> fill a bug report.
> Please note that native systemd support will be implemented with
> CASSANDRA-13148 and this is not strictly a RPM specific issue. We still
> intent to offer non-systemd support based on the already working init scripts
> that we ship. Therefor the first step is to make use of systemd backward
> compatibility for SysV/LSB scripts, so we can provide RPMs for both systemd
> and non-systemd environments.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
