[
https://issues.apache.org/jira/browse/CASSANDRA-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954685#comment-14954685
]
Sam Tunnicliffe commented on CASSANDRA-10498:
---------------------------------------------
It sounds very much as though the data for that particular user has been
written with a timestamp in the future. This shouldn't be possible unless the
data was inserted directly into the users table rather than using a {{CREATE
USER}} statement, or if it was done on a machine whose clock was wildly
incorrect. Either way, you can verify this by using {{sstable2json}} to export
the sstables for {{system_auth.users}} which you can then check the output of
that tool to see if the timestamp for that user's data is way ahead of the rest
of the data in the table. {{sstable2json}} operates on the local node, so
depending on the replication factor you'll need to figure out which nodes are
replicas for that particular row. You can do this with {{nodetool getendpoints
system_auth users <username>}}. Finally, you might want to force a compaction
for the table first so there's only a single sstable file to check.
> CREATE USER not inserting records in credentials table
> ------------------------------------------------------
>
> Key: CASSANDRA-10498
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10498
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Maitrayee
> Assignee: Sam Tunnicliffe
>
> We have 4 node 2.0.16 cluster using PasswordAuthenticator and
> CassandraAuthorizer
> Recently upgraded this cluster from 1.2.19.
> We have around 10 users with specific permissions.
> After upgrade, we are seeing only one user is missing from credentials table.
> Drop & recreate user did not help. Problem seems to be with this specific
> user/password.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
