mayadata-io / mayadata-io/oep-e2e

use case: OLAP databases on k8s on AWS that dynamically provisions EBS volumes

Open
#659 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog user story
Dominant language
Python
Stars
6
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I am running an OLAP database on K8s on AWS that dynamically provisions EBS volumes. Each volume is responsible for a shard of user data and I am looking to run around 100 volumes of 1TB each for a total database size of 100TB. What I don’t currently have is high availability. Would I get that by using OpenEBS? In other words, transparently to the dynamic volume provisioning process, I would have a RAID1 for each volume such that if one EBS disk fails, its mirror would continue to read/write without interruption of service (maybe with some degradation during resync after recovery). Can I use OpenEBS for this?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are mentioned. Start by reviewing OpenEBS documentation for Kubernetes dynamic provisioning with AWS EBS and the proposed replicated-volume setup. Done would be a clear, documented answer about whether this architecture provides uninterrupted service and how recovery behaves.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, databases, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.