opensearch-project/OpenSearch

[Feature Request] [Remote Store] Make metadata store independent of data store

Open

#12,919 opened on Mar 26, 2024

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Java (1,505 forks)batch import
Storage:Remoteenhancementgood first issue

Repository metrics

Stars
 (8,123 stars)
PR merge metrics
 (Avg merge 5d 9h) (266 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe

  • Currently, when we configure remote store for a cluster, both data and metadata (of segment, translog and cluster state) is stored in the same store.
  • But the access pattern and consistency requirements for data and metadata are different.
  • For example, data files are uploaded and downloaded by providing a filename whereas metadata is fetched based on certain characteristics such as recency.
  • Due to these differences, it is possible that metadata can be stored in a different data store (for example, a key-value store) as we store the data files in a blob store.

Describe the solution you'd like

The ideal solution should allow configuring a different remote store for metadata.

Related component

Storage:Remote

Describe alternatives you've considered

No response

Additional context

No response

Contributor guide

Research direction
Study the current remote store implementation in OpenSearch, focusing on how metadata (segment, translog, cluster state) and data files are stored. Design a configuration mechanism to allow separate remote stores for metadata and data, considering different access patterns and consistency requirements.
Tech stack
java
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaOpenSearch internalsRemote store concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20