New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple fixes in actors package #7119
Multiple fixes in actors package #7119
Conversation
1. Deactivate all actors in the app if the placement disconnects 2. Actor object now records the idle time rather than the last activation time 3. Remove actors from the active actors table even if deactivation fails 4. Improved shutdown of actors object Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
…ting readiness Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
…ctivation-refactorings
/ok-to-test |
/test-sdk-all |
Dapr E2E testCommit ref: 1488faa ✅ Build succeeded for linux/amd64
✅ Infrastructure deployed
✅ Build succeeded for windows/amd64
✅ Tests succeeded on windows/amd64
✅ Tests succeeded on linux/amd64
|
Dapr SDK Python testCommit ref: 1488faa ✅ Python SDK tests passed |
Dapr SDK Go testCommit ref: 1488faa ✅ Go SDK tests passed |
Dapr SDK Java testCommit ref: 1488faa ❌ Java SDK tests failedPlease check the logs for details on the error. |
Dapr SDK JS testCommit ref: 1488faa ❌ JS SDK tests failedPlease check the logs for details on the error. |
tests/integration/suite/actors/healthz/deactivate-on-unhealthy.go
Outdated
Show resolved
Hide resolved
Signed-off-by: Alessandro (Ale) Segala <43508+ItalyPaleAle@users.noreply.github.com>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #7119 +/- ##
==========================================
- Coverage 65.00% 64.86% -0.15%
==========================================
Files 221 221
Lines 20924 21003 +79
==========================================
+ Hits 13602 13623 +21
- Misses 6177 6225 +48
- Partials 1145 1155 +10 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First pass from me 🙂
tests/integration/suite/actors/healthz/deactivate-on-unhealthy.go
Outdated
Show resolved
Hide resolved
tests/integration/suite/actors/healthz/deactivate-on-unhealthy.go
Outdated
Show resolved
Hide resolved
tests/integration/suite/actors/healthz/deactivate-on-unhealthy.go
Outdated
Show resolved
Hide resolved
tests/integration/suite/actors/healthz/deactivate-on-unhealthy.go
Outdated
Show resolved
Hide resolved
tests/integration/suite/actors/healthz/deactivate-on-unhealthy.go
Outdated
Show resolved
Hide resolved
Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
@JoshVanL please review again :) |
@yaron2 along with https://github.com/dapr/dapr/pull/7119/files#diff-7ec21ca80e96c8603d65ab85ff72d4e3ef479f9cff11eb09f993182e1e91ce3a I think we need another int tests which checks that an actor is deactivated when the app reports unhealthy. This is contingent on #7022 and #6216 |
…ctivation-refactorings Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
I have fixed the merge conflicts. Is there anything else blocking this PR? Feedback on adding a new test is valid but not actionable at this stage. |
Yes, I think we should block until we have full test coverage for this, i.e. the app unhealthy actor deregister. |
Can it be done in a subsequent PR? |
Yes, please follow up on this @ItalyPaleAle |
@JoshVanL I was looking into adding a test based on your PR. Your PR reduces the healthcheck interval, but still requires 4 failed healthchecks, each on a 5s interval, for an app to be unhealthy. That makes the test still take at least 30s. Is there a way to make that faster? |
Yes, I think the current settings don't make much sense for even a "real" scenario and should be changed. |
Aside from "real" scenarios, perhaps there could be a way to tweak that (not sure how) so tests can set even lower values |
@ItalyPaleAle Unifying the health checks would make them configurable with the same CLI flags and therefore more testable. |
Makes sense. Will wait for that then |
This PR contains some fixes for actors. In order from the most "serious" one to the least: