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.

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

How can I extend the storage size after deployment? #4364

Alexander-He opened this issue May 18, 2017 · 4 comments


Copy link

@Alexander-He Alexander-He commented May 18, 2017

I have a situation, when I deploy my minio server, I don't know what storage size I need.

How can I extend the storage size after deployment?

Your Environment

  • Version used (minio version):
    Version: 2017-03-16T21:50:32Z
    Release-Tag: RELEASE.2017-03-16T21-50-32Z
    Commit-ID: 5311eb2
  • Server type and version:
    Deploy type : 4 minio nodes share 1 drive, 4 minio client are directly deploy on operating system.
  • Operating System and version (uname -a):
    Linux LFG1000644016 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  • Link to your project:

This comment has been minimized.

Copy link

@krishnasrinivas krishnasrinivas commented May 18, 2017

@Alexander-He you will have to launch a new minio instance with new storage and start using it.


This comment has been minimized.

Copy link

@nitisht nitisht commented May 18, 2017

@Alexander-He Minio recommends cloud-native approach for scaling your storage infrastructure. When you run out of storage, you simply spin new Minio instance(s) per tenant. A tenant can be a user, a group of users, or any other kind of aggregation of data.

Take for example, a CCTV video storage use case. Initially you wouldn't know how much storage you possibly need to store the videos. In such cases, you can assign one Minio instance to store videos from one month, another Minio instance to store videos for second month and so on. To make sure the application remembers which data is stored in which Minio instance, you can have a database storing the mapping from date-range to corresponding Minio instance.

This way you can scale infinitely, while your storage and application remain relatively simple.

Take a look at our multi-tenant deployment guide:

@deekoder deekoder added this to the Edge cache milestone May 18, 2017

This comment has been minimized.

Copy link

@deekoder deekoder commented May 18, 2017

Related to #4366


This comment has been minimized.

Copy link

@Alexander-He Alexander-He commented May 19, 2017

@nitisht I see, this helped me, thank you very much,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.