Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Refactor RemoteStoreRefreshListenerTests to use listener from IndexShard #12160

Closed
sachinpkale opened this issue Feb 5, 2024 · 1 comment
Closed

Refactor RemoteStoreRefreshListenerTests to use listener from IndexShard #12160

sachinpkale opened this issue Feb 5, 2024 · 1 comment
Labels
enhancement Enhancement or improvement to existing feature or request Storage:Durability Issues and PRs related to the durability framework untriaged

Comments

@sachinpkale
Copy link
Member

Is your feature request related to a problem? Please describe

#12157 (comment)

Describe the solution you'd like

Test should use RemoteStoreRefreshListener instance from IndexShard

Related component

Storage:Durability

Describe alternatives you've considered

No response

Additional context

No response
@sachinpkale sachinpkale added enhancement Enhancement or improvement to existing feature or request untriaged Storage:Durability Issues and PRs related to the durability framework and removed untriaged labels Feb 5, 2024
@sachinpkale sachinpkale mentioned this issue Feb 5, 2024
Merged
8 tasks
@peternied
Copy link
Member

[Triage - attendees 1 2 3 4]
@sachinpkale Thanks for creating this issue; however, it isn't being accepted due to not having enough details in this issue. Please feel free to re-open after addressing the reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Enhancement or improvement to existing feature or request Storage:Durability Issues and PRs related to the durability framework untriaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sachinpkale @peternied