Skip to content

[GCS]Fix TestActorTableResubscribe bug#11463

Merged
rkooo567 merged 1 commit intoray-project:masterfrom
antgroup:fix_TestActorTableResubscribe
Oct 21, 2020
Merged

[GCS]Fix TestActorTableResubscribe bug#11463
rkooo567 merged 1 commit intoray-project:masterfrom
antgroup:fix_TestActorTableResubscribe

Conversation

@ffbin
Copy link
Copy Markdown
Contributor

@ffbin ffbin commented Oct 19, 2020

Why are these changes needed?

GCS will not reply when actor registration fails, so when GCS restarts, gcs client will register the actor again. When an actor is registered, the status in GCS is DEPENDENCIES_UNREADY. When GCS finds that the owner of an actor is nil, it will destroy the actor and the status of the actor will change to DEAD. The GCS client fetch actor info from the GCS server, and the status of the actor may be DEPENDENCIES_UNREADY or DEAD, so we do not assert the actor status here any more.

Related issue number

Checks

  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@ffbin ffbin requested a review from rkooo567 October 19, 2020 12:45
@ffbin
Copy link
Copy Markdown
Contributor Author

ffbin commented Oct 20, 2020

Hi @rkooo567 , please help take a look, thanks :)

@rkooo567
Copy link
Copy Markdown
Contributor

@ffbin Does this mean there will be a DEAD message eventually? If this is not guaranteed, it can cause issues in real app right?

@ffbin
Copy link
Copy Markdown
Contributor Author

ffbin commented Oct 20, 2020

@ffbin Does this mean there will be a DEAD message eventually? If this is not guaranteed, it can cause issues in real app right?

Yeah, there will be a DEAD message in real app.

@rkooo567 rkooo567 merged commit a075e37 into ray-project:master Oct 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants