You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by rajasekhar kommineni <ra...@gmail.com> on 2018/07/09 18:23:22 UTC
Installation
Hello All,
I have a cassandra cluster where package installation is done, I want to convert it to tar.gz installation. Is there any procedure to follow.
Thanks,
Rajasekhar Kommineni
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
Re: Installation
Posted by rajasekhar kommineni <ra...@gmail.com>.
Thanks Michael, While I agree with the advantage of symlinks , I am worried for future upgrades.
My concern here is how to unlink the Cassandra binaries like nodetool,cassandra ,cqlsh etc after migrating to tar gz installation.
Thanks,
> On Jul 10, 2018, at 5:46 AM, Michael Shuler <mi...@pbandjelly.org> wrote:
>
> 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=</path/to/extracted/tarball>
> 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-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
Re: Installation
Posted by Michael Shuler <mi...@pbandjelly.org>.
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=</path/to/extracted/tarball>
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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
Re: Installation
Posted by rajasekhar kommineni <ra...@gmail.com>.
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
$
Thanks,
> On Jul 10, 2018, at 12:28 AM, Rahul Singh <ra...@gmail.com> wrote:
>
> That approach will work, however that may take a long time.
>
> The important things that are unique to your cluster will be your configuration files & your data /log directories.
>
> The binaries can be placed on the same machines via tar installation. While keeping the machines running on the old binaries, you can migrate the data / log new directories. If you move your data, you can use links in linux to point the old directories to the new locations.
>
> Once this is done, you can configure your tar installation to point to your new data directories, and turn off the old binaries and turn on the new binaries, one node at a time.
>
>
> --
> Rahul Singh
> rahul.singh@anant.us
>
> Anant Corporation
> On Jul 9, 2018, 6:35 PM -0500, rajpal reddy <ra...@gmail.com>, wrote:
>> We have our infrastructure in cloud so opted for adding new dc with tar.gz then removed the old dc with package installation
>>
>> Sent from my iPhone
>>
>>> On Jul 9, 2018, at 2:23 PM, rajasekhar kommineni <ra...@gmail.com> wrote:
>>>
>>> Hello All,
>>>
>>> I have a cassandra cluster where package installation is done, I want to convert it to tar.gz installation. Is there any procedure to follow.
>>>
>>> Thanks,
>>> Rajasekhar Kommineni
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
>>> For additional commands, e-mail: user-help@cassandra.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: user-help@cassandra.apache.org
>>
Re: Installation
Posted by Rahul Singh <ra...@gmail.com>.
That approach will work, however that may take a long time.
The important things that are unique to your cluster will be your configuration files & your data /log directories.
The binaries can be placed on the same machines via tar installation. While keeping the machines running on the old binaries, you can migrate the data / log new directories. If you move your data, you can use links in linux to point the old directories to the new locations.
Once this is done, you can configure your tar installation to point to your new data directories, and turn off the old binaries and turn on the new binaries, one node at a time.
--
Rahul Singh
rahul.singh@anant.us
Anant Corporation
On Jul 9, 2018, 6:35 PM -0500, rajpal reddy <ra...@gmail.com>, wrote:
> We have our infrastructure in cloud so opted for adding new dc with tar.gz then removed the old dc with package installation
>
> Sent from my iPhone
>
> > On Jul 9, 2018, at 2:23 PM, rajasekhar kommineni <ra...@gmail.com> wrote:
> >
> > Hello All,
> >
> > I have a cassandra cluster where package installation is done, I want to convert it to tar.gz installation. Is there any procedure to follow.
> >
> > Thanks,
> > Rajasekhar Kommineni
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: user-help@cassandra.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
Re: Installation
Posted by rajpal reddy <ra...@gmail.com>.
We have our infrastructure in cloud so opted for adding new dc with tar.gz then removed the old dc with package installation
Sent from my iPhone
> On Jul 9, 2018, at 2:23 PM, rajasekhar kommineni <ra...@gmail.com> wrote:
>
> Hello All,
>
> I have a cassandra cluster where package installation is done, I want to convert it to tar.gz installation. Is there any procedure to follow.
>
> Thanks,
> Rajasekhar Kommineni
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org