On 2019/02/22 23:31:01, Timothy Palpant wrote:
> I am trying to use `nodetool stopdaemon` to stop Cassandra but hitting the
> following error:
>
> ```
> $ cassandra_ctl nodetool -h 127.0.0.1 -p 5100 stopdaemon
> error: null
> -- StackTrace --
> java.lang.NullPointerException
> at
>
Hi Alex,
We wrote a blog post on this topic late last year:
http://thelastpickle.com/blog/2018/09/18/assassinate.html.
In short, you will need to run the assassinate command on each node
simultaneously a number of times in quick succession. This will generate a
number of messages requesting all
I'm afraid I get the same error when navigating to /usr/bin and running
./nodetool help
I'm definitely running Java 8 and Cassandra 3.11.4.
I'm wondering if I did something when installing Oracle Java 11 to run
Hadoop that is interfering, but that's all under another username. There is
nothing
On further reading it does look like there may be a problem with your Java
setup, as others are reporting this with Java 9 and above.
You could try the 3rd answer here and see if this helps:
https://stackoverflow.com/questions/48193965/cassandra-nodetool-java-lang-nullpointerexception
> On 3
Same result it seems:
Welcome to JMX terminal. Type "help" for available commands.
$>open localhost:7199
#Connection to localhost:7199 is opened
$>bean org.apache.cassandra.net:type=Gossiper
#bean is set to org.apache.cassandra.net:type=Gossiper
$>run unsafeAssassinateEndpoint 192.168.1.18
My users has permissions to read everything in /etc/cassandra.
However, it gave me an idea. When I run sudo nodetool status, it works, I
get the "UN" status.
Not sure if this permissions issue will interfere with my use of Cassandra
or not. Do I have to change the permissions of the
On Wed, Apr 3, 2019 at 4:23 PM David Taylor wrote:
>
> $ nodetest status
> error: null
> -- StackTrace --
> java.lang.NullPointerException
> at
> org.apache.cassandra.config.DatabaseDescriptor.getDiskFailurePolicy(DatabaseDescriptor.java:1892)
>
Could it be that your user doesn't have
Hi Paul thanks for responding.
I created a ~/.cassandra directory and chmodded it to 777
in /var/log/cassandra/system.log the only non-INFO items are:
WARN [main] 2019-04-03 11:47:54,172 StartupChecks.java:136 - jemalloc
shared library could not be preloaded to speed up memory allocations
WARN
On Wed, Apr 3, 2019 at 4:37 PM Saleil Bhat (BLOOMBERG/ 731 LEX) <
sbha...@bloomberg.net> wrote:
>
> Thanks for the reply! One clarification: the replacement node WOULD be
> DC-local as far as Cassandra is is concerned; it would just be in a
> different physical DC. Using the Orlando -> Tampa
David,
When you start cassandra all the logs go to system.log normally in the
/var/log/cassandra directory, so you should look there once it has started, to
check everything is ok.
I assume you mean you ran nodetool status rather than nodetest.
The nodetool command stores a history of
Run assassinate the old way. I works very well...
wget -q -O jmxterm.jar
http://downloads.sourceforge.net/cyclops-group/jmxterm-1.0-alpha-4-uber.jar
java -jar ./jmxterm.jar
$>open localhost:7199
$>bean org.apache.cassandra.net:type=Gossiper
$>run unsafeAssassinateEndpoint 192.168.1.18
Hello,
Short story:
- I had to replace a dead node in my cluster
- 1 week after, dead node is still seen as DN by 3 out of 5 nodes
- dead node has null host_id
- assassinate on dead node fails with error
How can I get rid of this dead node ?
Long story:
I had a 3 nodes cluster (Cassandra 3.9)
Hey,
Thanks for the reply! One clarification: the replacement node WOULD be DC-local
as far as Cassandra is is concerned; it would just be in a different physical
DC. Using the Orlando -> Tampa example, suppose my DC was named 'floridaDC' in
Cassandra. Then I would just kill a node in
I am running a System87 Oryx Pro laptop with Ubuntu 18.04
I had only Oracle Java 11 installed for Hadoop, so I also installed
OpenJDK8 with:
$ sudo apt-get install openjdk-8-jre
and switched to it with
$ sudo update-java-alternatives --set
path/shown/with/"update-java-alternatives --list"
$
Saleil,
Are you performing any regular repairs on the existing cluster?
If you are, you could set this repair up on the Tampa cluster, then after all
the applications have been switched to Tampa, wait for a complete repair cycle,
then it will be safe to decommission Orlando. however, there
On Wed, 3 Apr 2019 at 18:38, Oleksandr Shulgin
wrote:
>
> On Wed, Apr 3, 2019 at 12:28 AM Saleil Bhat (BLOOMBERG/ 731 LEX)
> wrote:
>>
>>
>> The standard procedure for doing this seems to be add a 3rd datacenter to
>> the cluster, stream data to the new datacenter via nodetool rebuild, then
Hi Oleksandr,
Yes, that was always the case. All older versions are removed from Debian repo
index :(
From: Oleksandr Shulgin
Reply-To: "user@cassandra.apache.org"
Date: Tuesday, April 2, 2019 at 20:04
To: User
Subject: How to install an older minor release?
Hello,
We've just noticed that
On Wed, Apr 3, 2019 at 12:28 AM Saleil Bhat (BLOOMBERG/ 731 LEX) <
sbha...@bloomberg.net> wrote:
>
> The standard procedure for doing this seems to be add a 3rd datacenter to
> the cluster, stream data to the new datacenter via nodetool rebuild, then
> decommission the old datacenter. A more
18 matches
Mail list logo
