[jira] [Updated] (CASSANDRA-15177) Reloading of auth caches happens on the calling thread
[
https://issues.apache.org/jira/browse/CASSANDRA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15177:
Fix Version/s: (was: 4.0-rc)
4.0-beta5
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/d656f8ac012f4577d22ed7bd3db94c15ae8eb5a9
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thanks, committed to trunk in {{d656f8ac012f4577d22ed7bd3db94c15ae8eb5a9}}
> Reloading of auth caches happens on the calling thread
> --
>
> Key: CASSANDRA-15177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15177
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Authorization
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 4.0-beta5
>
>
> When Guava caches were replaced by their Caffeine equivalents in
> CASSANDRA-10855, the async reloading of stale AuthCache entries was lost due
> to the use of {{MoreExecutors.directExecutor()}} to provide the delegate
> executor. Under normal conditions, we can expect these operations to be
> relatively expensive, and in failure scenarios where replicas for the auth
> data are DOWN this will greatly increase latency, so they shouldn’t be done
> on threads servicing requests.
--
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
[jira] [Updated] (CASSANDRA-15177) Reloading of auth caches happens on the calling thread
[
https://issues.apache.org/jira/browse/CASSANDRA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-15177:
---
Status: Ready to Commit (was: Review In Progress)
> Reloading of auth caches happens on the calling thread
> --
>
> Key: CASSANDRA-15177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15177
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Authorization
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 4.0-rc
>
>
> When Guava caches were replaced by their Caffeine equivalents in
> CASSANDRA-10855, the async reloading of stale AuthCache entries was lost due
> to the use of {{MoreExecutors.directExecutor()}} to provide the delegate
> executor. Under normal conditions, we can expect these operations to be
> relatively expensive, and in failure scenarios where replicas for the auth
> data are DOWN this will greatly increase latency, so they shouldn’t be done
> on threads servicing requests.
--
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
[jira] [Updated] (CASSANDRA-15177) Reloading of auth caches happens on the calling thread
[
https://issues.apache.org/jira/browse/CASSANDRA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-15177:
---
Reviewers: Benjamin Lerer, Brandon Williams, Benjamin Lerer (was: Benjamin
Lerer, Brandon Williams)
Benjamin Lerer, Brandon Williams, Benjamin Lerer
Status: Review In Progress (was: Patch Available)
> Reloading of auth caches happens on the calling thread
> --
>
> Key: CASSANDRA-15177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15177
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Authorization
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 4.0-rc
>
>
> When Guava caches were replaced by their Caffeine equivalents in
> CASSANDRA-10855, the async reloading of stale AuthCache entries was lost due
> to the use of {{MoreExecutors.directExecutor()}} to provide the delegate
> executor. Under normal conditions, we can expect these operations to be
> relatively expensive, and in failure scenarios where replicas for the auth
> data are DOWN this will greatly increase latency, so they shouldn’t be done
> on threads servicing requests.
--
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
[jira] [Updated] (CASSANDRA-15177) Reloading of auth caches happens on the calling thread
[
https://issues.apache.org/jira/browse/CASSANDRA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15177:
Fix Version/s: 4.0-rc
> Reloading of auth caches happens on the calling thread
> --
>
> Key: CASSANDRA-15177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15177
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Authorization
>Reporter: Sam Tunnicliffe
>Priority: Normal
> Fix For: 4.0-rc
>
>
> When Guava caches were replaced by their Caffeine equivalents in
> CASSANDRA-10855, the async reloading of stale AuthCache entries was lost due
> to the use of {{MoreExecutors.directExecutor()}} to provide the delegate
> executor. Under normal conditions, we can expect these operations to be
> relatively expensive, and in failure scenarios where replicas for the auth
> data are DOWN this will greatly increase latency, so they shouldn’t be done
> on threads servicing requests.
--
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
[jira] [Updated] (CASSANDRA-15177) Reloading of auth caches happens on the calling thread
[
https://issues.apache.org/jira/browse/CASSANDRA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15177:
Authors: Sam Tunnicliffe
Impacts: (was: None)
Test and Documentation Plan: Covered by existing python dtests
Status: Patch Available (was: Open)
I had forgotten about this, but we ought to fix it before rc. Reloading
eligible items on a thread servicing user requests can cause timeouts and
unavailables.
[patch|https://github.com/beobal/cassandra/commits/15177-trunk],
[circle|https://app.circleci.com/pipelines/github/beobal/cassandra?branch=cci%2F15177-trunk],
[ci-c.a.o|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/500]
> Reloading of auth caches happens on the calling thread
> --
>
> Key: CASSANDRA-15177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15177
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Authorization
>Reporter: Sam Tunnicliffe
>Priority: Normal
>
> When Guava caches were replaced by their Caffeine equivalents in
> CASSANDRA-10855, the async reloading of stale AuthCache entries was lost due
> to the use of {{MoreExecutors.directExecutor()}} to provide the delegate
> executor. Under normal conditions, we can expect these operations to be
> relatively expensive, and in failure scenarios where replicas for the auth
> data are DOWN this will greatly increase latency, so they shouldn’t be done
> on threads servicing requests.
--
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
[jira] [Updated] (CASSANDRA-15177) Reloading of auth caches happens on the calling thread
[
https://issues.apache.org/jira/browse/CASSANDRA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15177:
Severity: Normal
Complexity: Normal
Discovered By: New Unit Test
Bug Category: Parent values: Degradation(12984)Level 1 values: Performance
Bug/Regression(12997)
Component/s: (was: Legacy/Local Write-Read Paths)
Status: Open (was: Triage Needed)
> Reloading of auth caches happens on the calling thread
> --
>
> Key: CASSANDRA-15177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15177
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Authorization
>Reporter: Sam Tunnicliffe
>Priority: Normal
>
> When Guava caches were replaced by their Caffeine equivalents in
> CASSANDRA-10855, the async reloading of stale AuthCache entries was lost due
> to the use of {{MoreExecutors.directExecutor()}} to provide the delegate
> executor. Under normal conditions, we can expect these operations to be
> relatively expensive, and in failure scenarios where replicas for the auth
> data are DOWN this will greatly increase latency, so they shouldn’t be done
> on threads servicing requests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
