cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12364) dtest failure in upgrade_tests.paging_test.TestPagingDatasetChangesNodes3RF3_Upgrade_current_3_x_To_indev_3_x.test_cell_TTL_expiry_during_paging
Date Tue, 13 Sep 2016 15:00:25 GMT


Sylvain Lebresne commented on CASSANDRA-12364:

bq.  Is it safe in the general case to ignore {{RejectedExecutionException}}s in the logs

In theory, not really. In practice, kind of. I mean, ideally we should make sure this never
happen as it's not particularly useful, and potentially scary, for users and I'm all for doing
so. But we're all busy with more important things (for the reasons I mentioned above, it's
almost surely only cosmetic) so I'm mainly arguing that it's probably not worth failing perfectly
good tests on that while we get to fixing it.

Anyway, my advise is: ignore it in the tests (at least on nodes we know are shut down, assuming
we can easily do so) but rename that ticket or create a new one to "Make sure we never throw

> dtest failure in upgrade_tests.paging_test.TestPagingDatasetChangesNodes3RF3_Upgrade_current_3_x_To_indev_3_x.test_cell_TTL_expiry_during_paging
> ------------------------------------------------------------------------------------------------------------------------------------------------
>                 Key: CASSANDRA-12364
>                 URL:
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Sean McCarthy
>            Assignee: Russ Hatch
>              Labels: dtest
>         Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, node2_debug.log,
node2_gc.log, node3.log, node3_debug.log, node3_gc.log
> example failure:
> {code}
> Error Message
> Unexpected error in log, see stdout
> {code}
> {code}
> Standard Output
> git:5051c0f6eb3f984600600c9577d6b5ece9038c74
> Unexpected error in node1 log, error: 
> ERROR [InternalResponseStage:4] 2016-07-28 03:23:02,097 - Exception
in thread Thread[InternalResponseStage:4,5,main]
> java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut down
> 	at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(
> 	at java.util.concurrent.ThreadPoolExecutor.reject( ~[na:1.8.0_51]
> 	at java.util.concurrent.ThreadPoolExecutor.execute( ~[na:1.8.0_51]
> 	at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.execute(
> 	at org.apache.cassandra.db.ColumnFamilyStore.waitForFlushes(
> 	at org.apache.cassandra.db.ColumnFamilyStore.forceFlush(
> 	at org.apache.cassandra.schema.SchemaKeyspace.lambda$flush$1(
> 	at org.apache.cassandra.schema.SchemaKeyspace$$Lambda$200/2113926365.accept(Unknown
Source) ~[na:na]
> 	at java.lang.Iterable.forEach( ~[na:1.8.0_51]
> 	at org.apache.cassandra.schema.SchemaKeyspace.flush( ~[apache-cassandra-3.7.jar:3.7]
> 	at org.apache.cassandra.schema.SchemaKeyspace.mergeSchema(
> 	at org.apache.cassandra.schema.SchemaKeyspace.mergeSchemaAndAnnounceVersion(
> 	at org.apache.cassandra.service.MigrationTask$1.response( ~[apache-cassandra-3.7.jar:3.7]
> 	at
> 	at ~[apache-cassandra-3.7.jar:3.7]
> 	at java.util.concurrent.Executors$ ~[na:1.8.0_51]
> 	at ~[na:1.8.0_51]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker( ~[na:1.8.0_51]
> 	at java.util.concurrent.ThreadPoolExecutor$ [na:1.8.0_51]
> 	at [na:1.8.0_51]
> {code}
> Related failures:

This message was sent by Atlassian JIRA

View raw message