[
https://issues.apache.org/jira/browse/CASSANDRA-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397193#comment-13397193
]
David B commented on CASSANDRA-4356:
------------------------------------
Unfortunately I had to manually delete the earlier column family to run another
test. But with this particular cluster it is easily reproduced. I get the
same error, but this time the "invalid UTF8 bytes" is '4fe11f78'.
Unfortunately "list schema_columnfamilies" doesn't seem to provide much help.
Here is what I get:
[default@unknown] use MyKeyspace
... ;
Authenticated to keyspace: MyKeyspace
[default@MyKeyspace] describe;
Keyspace: MyKeyspace:
Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
Durable Writes: true
Options: [replication_factor:2]
Column Families:
ColumnFamily: MyColumnFamily
Key Validation Class: org.apache.cassandra.db.marshal.LongType
Default column value validator: org.apache.cassandra.db.marshal.BytesType
Columns sorted by: org.apache.cassandra.db.marshal.BytesType
GC grace seconds: 864000
Compaction min/max thresholds: 4/32
Read repair chance: 0.1
DC Local Read repair chance: 0.0
Replicate on write: true
Caching: KEYS_ONLY
Bloom Filter FP chance: default
Built indexes: []
Compaction Strategy:
org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy
Compression Options:
chunk_length_kb: 64
sstable_compression: org.apache.cassandra.io.compress.SnappyCompressor
null
[default@MyKeyspace] use system;
Authenticated to keyspace: system
[default@system] list schema_columnfamilies;
Using default limit of 100
Using default column limit of 100
-------------------
RowKey: galaxy_lookups
-------------------
RowKey: MyKeyspace
2 Rows Returned.
Elapsed time: 32 msec(s).
Now, if I restart the affected node, it no longer appears as a column family
when I do "use MyKeyspace; describe;". However, the data files are still in
the data/MyKeyspace/MyColumnFamily directory.
> Drop column family fail in Cassandra 1.1.1
> ------------------------------------------
>
> Key: CASSANDRA-4356
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4356
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.1
> Environment: 2-node cluster running on Ubuntu 10.10
> Reporter: David B
> Assignee: Sylvain Lebresne
>
> 2-node v1.1.1 cluster. Attempts to drop column families appears to succeed,
> but fails behind the scenes. More specifically, the column family is deleted
> as follows:
> cassandra-cli -h HOST_1
> > use MyKeyspace
> > drop column family MyColumnFamily
> 79f7ab8c-da08-355c-87a0-8e9630eb4945
> Waiting for schema agreement...
> ... schemas agree across the cluster
> Data files in fact have been deleted on HOST_1. However, the files on HOST_2
> still exist in the /data directory. Also, the following stack trace appears
> in /var/log/system.log on HOST_2:
> ERROR [MigrationStage:1] 2012-06-19 22:05:56,172 AbstractCassandraDaemon.java
> (line 134) Exception in thread Thread[MigrationStage:1,5,main]
> org.apache.cassandra.cql.jdbc.MarshalException: invalid UTF8 bytes 4fe0f7c7
> at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:81)
> at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
> at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
> at
> org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
> at
> org.apache.cassandra.config.CFMetaData.fromSchemaNoColumns(CFMetaData.java:1170)
> at
> org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1215)
> at
> org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:291)
> at
> org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:396)
> at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:271)
> at
> org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:249)
> at
> org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> From this point on, all other Migration commands (e.g. creating new column
> families) similarly report no errors in cassandra-cli, but fail behind the
> scenes. Recovering from the erroneous state requires a cluster restart.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
