Restarting the Cassandra service resolved this issue. Thanks for your advice!
Sincerely,
Myron A. Semack
From: kurt greaves [mailto:k...@instaclustr.com]
Sent: Tuesday, August 15, 2017 6:10 PM
To: User <user@cassandra.apache.org>
Subject: Re: Attempted to write commit log
Myron, it just means that while the node was down, one of the tables got
dropped. When you eventually brought the node back online and the commit
logs were getting replayed, it tried to replay a mutation for a table which
no longer exists. Cheers!
On Wed, Aug 16, 2017 at 5:56 AM, Myron A. Semack
what does nodetool describecluster show?
stab in the dark but you could try nodetool resetlocalschema or a rolling
restart of the cluster if it's schema issues.
