apache / apache/iotdb

Autoscaling plan for IoTDB (e.g. on Azure)

Ouverte
#4,254 1 commentaire 3 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Java
Étoiles
6.4k
Forks
1.2k
Merge moyen
1 j 23 h
PR mergées (30 j)
115

Description

**Is your feature request related to a problem? Please describe.**

At our company, we want to have most of our services as managed services. This makes maintenance very effective on our side as we do not have to employ more people to keep the infrastructure running. Currently this is a blocker for integrating IoTDB, as everything around this database would have to be managed and scaled manually.

**Describe the solution you'd like**

A part of the documentation, describing an example of how to set up IoTDB by using only auto-scaling modules of a cloud provider - for me Azure would be the best example.

**Describe alternatives you've considered**

The documentation already has something about a Hadoop Cluster, which I could find as managed solution on Azure, but I don't know if it's a good solution (price-vise) and if it will scale automatically with our demands.

**Additional context**

Any hint is also very welcome!

As I understand, integrating the storage as a managed storage would already be a huge improvement - like a storage abstraction which is compatible with Azure Storage.

For the IoTDB instance itself my first thought was to set up a VM scale set, which will add new VMs to a cluster as certain limits (e.g. in CPU usage) are reached. If this whole idea of mine is just not the right way, I'm thrilled to get your input.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par la documentation existante de Hadoop Cluster et étudiez les alternatives gérées par Azure, notamment les VM scale sets et le stockage géré. Déterminez si un déploiement IoTDB avec autoscaling est viable et documentez un exemple concret sur Azure, notamment l’approche de stockage, le comportement de la mise à l’échelle et les compromis pertinents.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
azure, hadoop
Domaine
cloud, databases, documentation
Type d'issue
Documentation
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.