Skip to content

[GCS]Delete redis accessor module#9898

Closed
kisuke95 wants to merge 26 commits intoray-project:masterfrom
antgroup:delete_redis_module
Closed

[GCS]Delete redis accessor module#9898
kisuke95 wants to merge 26 commits intoray-project:masterfrom
antgroup:delete_redis_module

Conversation

@kisuke95
Copy link
Copy Markdown
Member

@kisuke95 kisuke95 commented Aug 4, 2020

Why are these changes needed?

Delete the old rediss accessor module, which is not needed. Now, we use GCS table storage instead to handle requests.

In order to remove RedisGcsClient, there still some test files to be modified.

  • object_manager_stress_test.cc
  • object_manager_test.cc
  • object_manager_integration_test.cc

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/latest/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failure rates at https://ray-travis-tracker.herokuapp.com/.
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested (please justify below)

@AmplabJenkins
Copy link
Copy Markdown

Can one of the admins verify this patch?

@AmplabJenkins
Copy link
Copy Markdown

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/29357/
Test FAILed.

@rkooo567 rkooo567 self-assigned this Aug 4, 2020
@AmplabJenkins
Copy link
Copy Markdown

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/29423/
Test FAILed.

@ffbin ffbin self-assigned this Aug 5, 2020
@ffbin ffbin self-requested a review August 5, 2020 07:00
CI_KEEP_ALIVE: Travis
@AmplabJenkins
Copy link
Copy Markdown

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/29434/
Test FAILed.

@kisuke95 kisuke95 changed the title [WIP] Delete redis module Delete redis module Aug 5, 2020
@ffbin ffbin changed the title Delete redis module [GCS]Delete redis module Aug 6, 2020
@ffbin
Copy link
Copy Markdown
Contributor

ffbin commented Aug 6, 2020

RedisGcsClient does not need to inherit GcsClient, and maybe we can remove it, because we can use RedisClient directly. @rkooo567 What's your suggestion?

@rkooo567
Copy link
Copy Markdown
Contributor

rkooo567 commented Aug 6, 2020

@kisuke95 Can you update the description?

@ffbin Isn't it going to cause troubles when we support multiple backends if we just directly use RedisClient?

@AmplabJenkins
Copy link
Copy Markdown

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/29505/
Test FAILed.

@ffbin
Copy link
Copy Markdown
Contributor

ffbin commented Aug 7, 2020

@kisuke95 Can you update the description?

@ffbin Isn't it going to cause troubles when we support multiple backends if we just directly use RedisClient?

RedisGcsClient is compatible with redis module. We now use ServiceBasedGcsClient, so RedisGcsClient can be removed.

Copy link
Copy Markdown
Contributor

@rkooo567 rkooo567 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ffbin Ah, I see. So you mean we can just use ServiceBasedAccessor for testing and completely remove RedisGcsClient because we won't need it anymore right? It seems like gcs_server -> Redis is done by redis_store_client, so I think it is fine to remove.

Also, it seems like we are writing mock accessor per tests. Is there any way we can just collect all mock accessors in a single file (or dir) and just import them to test files? I assume they are usually resuable.

@AmplabJenkins
Copy link
Copy Markdown

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/29730/
Test FAILed.

@rkooo567
Copy link
Copy Markdown
Contributor

Hey @kisuke95 If the PR is ready to be reviewed again, please remove the tag (author action required)!

@kisuke95 kisuke95 removed the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Aug 12, 2020
@kisuke95 kisuke95 requested a review from rkooo567 August 12, 2020 09:20
Copy link
Copy Markdown
Contributor

@rkooo567 rkooo567 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM in general! Just a few small comments. I will let @ffbin sign off the PR since he should be more familiar with this code path.

return ms_since_epoch.count();
}

class MockGcsClient : public gcs::RedisGcsClient {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ffbin Didn't you mention we should use RedisClient directly? Is it still applied?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can remove RedisGcsClient directly.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kisuke95 Can you address this part?

@rkooo567 rkooo567 added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Aug 12, 2020
@ffbin ffbin removed the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Aug 13, 2020
@kisuke95
Copy link
Copy Markdown
Member Author

Also, it seems like we are writing mock accessor per tests. Is there any way we can just collect all mock accessors in a single file (or dir) and just import them to test files? I assume they are usually resuable.

@rkooo567 So I put them in a header file, and import it in *.test.cc file

@kisuke95 kisuke95 changed the title [GCS]Delete redis module [GCS]Delete redis accessor module Aug 13, 2020
@rkooo567
Copy link
Copy Markdown
Contributor

I will mark the PR as author action required as @ffbin said we can remove RdisGCSClient. I think if we don't do this in this PR, we will never do that, so I am favorable doing it if it can remove good amount of code.

Please remove the tag if you think it is unnecessary (or if you remove RedisGCSClient).

@rkooo567 rkooo567 added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Aug 14, 2020
@kisuke95
Copy link
Copy Markdown
Member Author

I will mark the PR as author action required as @ffbin said we can remove RdisGCSClient. I think if we don't do this in this PR, we will never do that, so I am favorable doing it if it can remove good amount of code.

Please remove the tag if you think it is unnecessary (or if you remove RedisGCSClient).

@rkooo567 I'm an intern of Alipay, now I'm preparing for my report on work to become a regular staff. I will remove RedisGcsClient after it.

@rkooo567
Copy link
Copy Markdown
Contributor

No worries @kisuke95 Good luck on your report :)! Please take your time and re-ping me or remove a author-action-required tag whenever you are ready.

@kfstorm
Copy link
Copy Markdown
Member

kfstorm commented Nov 3, 2020

@ffbin Will somebody take on this work?

@rkooo567
Copy link
Copy Markdown
Contributor

rkooo567 commented Nov 3, 2020

@kfstorm thanks for bringing this up. I’d like to finish this pr asap.

@ffbin
Copy link
Copy Markdown
Contributor

ffbin commented Nov 3, 2020

@ffbin Will somebody take on this work?

We will continue to complete this pr. I prefer to split this pr. At present, there are many modified PR files and the merging cycle is relatively long.

@clay4megtr clay4megtr self-assigned this Dec 18, 2020
@clay4megtr
Copy link
Copy Markdown
Contributor

I will task over this work, cc @ffbin @rkooo567 @kfstorm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

@author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants