[ 
https://issues.apache.org/jira/browse/CASSANDRA-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161586#comment-17161586
 ] 

David Capwell commented on CASSANDRA-15191:
-------------------------------------------

python dtests failed; it looks like exceptions were not logged before and all 
are logged now.  Simple example is with the auth tests found in 
https://app.circleci.com/pipelines/github/dcapwell/cassandra/297/workflows/aefdb912-4395-498a-a1b6-b16770d46a45/jobs/1438
 

test_udf_permissions_validation - auth_test.TestAuthRoles

{code}
Unexpected error found in node logs (see stdout for full details). Errors: 
[ERROR [Native-Transport-Requests-11] 2020-07-20 21:51:31,717 
JVMStabilityInspector.java:81 - Uncaught exception in thread 
Thread[Native-Transport-Requests-11,10,main]
org.apache.cassandra.exceptions.UnauthorizedException: User mike has no ALTER 
permission on <function ks.plus_one(int)> or any of its parents
        at 
org.apache.cassandra.service.ClientState.ensurePermissionOnResourceChain(ClientState.java:430)
        at 
org.apache.cassandra.service.ClientState.ensurePermission(ClientState.java:404)
        at 
org.apache.cassandra.cql3.statements.schema.CreateFunctionStatement.authorize(CreateFunctionStatement.java:177)
        at 
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:203)
        at 
org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:253)
        at 
org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:240)
        at 
org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:108)
        at 
org.apache.cassandra.transport.Message$Request.execute(Message.java:253)
        at 
org.apache.cassandra.transport.Message$Dispatcher.processRequest(Message.java:725)
        at 
org.apache.cassandra.transport.Message$Dispatcher.lambda$channelRead0$0(Message.java:630)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at 
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
        at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
        at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
{code}

This exception wasn't logged before and was sent back to the user, with this 
patch we now log all these hidden exceptions.

> stop_paranoid disk failure policy is ignored on CorruptSSTableException after 
> node is up
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-15191
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15191
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Config
>            Reporter: Vincent White
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>             Fix For: 3.11.x, 4.0-beta
>
>         Attachments: log.txt
>
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> There is a bug when disk_failure_policy is set to stop_paranoid and 
> CorruptSSTableException is thrown after server is up. The problem is that 
> this setting is ignored. Normally, it should stop gossip and transport but it 
> just continues to serve requests and an exception is just logged.
>  
> This patch unifies the exception handling in JVMStabilityInspector and code 
> is reworked in such way that this inspector acts as a central place where 
> such exceptions are inspected. 
>  
> The core reason for ignoring that exception is that thrown exception in 
> AbstractLocalAwareExecturorService is not CorruptSSTableException but it is 
> RuntimeException and that exception is as its cause. Hence it is better if we 
> handle this in JVMStabilityInspector which can recursively examine it, hence 
> act accordingly.
> Behaviour before:
> stop_paranoid of disk_failure_policy is ignored when CorruptSSTableException 
> is thrown, e.g. on a regular select statement
> Behaviour after:
> Gossip and transport (cql) is turned off, JVM is still up for further 
> investigation e.g. by jmx.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to