Unsolved
This post is more than 5 years old
2 Intern
•
244 Posts
0
693
March 31st, 2014 05:00
Tell us your most important ViPR Support concerns or support challenges you face in deploying and supporting ViPR?
Hi,
As we are really excited about ViPR, we are also aware that support of ViPR will provide you some interesting opportunities and challenges.
We would very much like to hear from you as you employ ViPR in your environment.
What are your support experiences, your opportunities, your challenges.
What can we do to help improve your support experience?
Thanks.
No Events found!
Mabro1
2 Intern
•
666 Posts
0
March 31st, 2014 09:00
I am looking forward to a lively interactive discussion here. Often we share best practice discussions. But we'd love to to hear what your deployment was like for you, the customer. Share with us the highs and lows, the challenges.Tell us how it was to setup and how it's going now.
Cheers,
Mark
chris_arnett
110 Posts
0
April 1st, 2014 20:00
Sanjeev,
The Data Services storage engine does its own allocation management and will pre-allocate files in 128 MB chunks. When you create objects, ViPR will start to fill these chunks with data. For efficiency, when you delete objects, they are simply marked deleted and the space they consumed will be recycled for new writes. So these chunk files may appear to the VNX as consumed space, but that’s not entirely true. There is likely some portion of the pre-allocated files that is not filled with user data.
However, you make a good point that the space consumed by these chunks is still unavailable to anything other than Data Services. It's probably a good idea to employ some kind of strategy when creating and assigning data stores where Data Services are involved.