Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Storage space consideration for deploying AMS

avatar
Contributor

What are the guidelines around allocating storage space for AMS service?

A partner is looking for ballpark number for a small / medium and large cluster so they can ensure that they don't run out of storage space for AMS

1 ACCEPTED SOLUTION

avatar
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login
6 REPLIES 6

avatar
Master Mentor

603-screen-shot-2015-12-01-at-64208-pm.png

Please see the above. You want to make sure that it's pointing to correct file system with enough space. I would say 200GB to 300GB dedicated disk is good start for small cluster. Many times, installation ends up on root thats why its important to pay attention to the above setting.

@vsomani

avatar
Contributor

Thanks Neeraj

avatar
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login

avatar
Contributor

Thank you Ali. This document will definitely be useful for partner. Will share it with them

avatar

Thanks for asking the question...I learnt something new 🙂

avatar
Rising Star

While storage space is absolutely critical as @Neeraj Sabharwal and @Ali Bajwa wrote in their post we just "discovered" that also CPU is a key point. When HWX released AMS we began to deploy Ambari and AMS on the same machine, but soon the understood that for a production environment it could be a good practice to use one VM for Ambari and another VM for AMS, so the really high impact on computation resources of AMS didn't impact Ambari (sometimes, during the aggregation phase we got 16 CPU at 90% for 10/15 minutes).