I currently have some Nimble Streamers in production for a VOD website and I find that nimble is lacking control for the cache. My edges are currently running with a 30 days cache limit, because files rarely gets updated. But when a mistake occurs and I need to update a file (bad encoding / bitrate), I can't easily erase the cache of all my streamers. And at this time, we can't even wipe the cache without doing a restart of the nimble service.
So in a VOD context, I find it important to have a way to invalidate a stream cache easily for all the edges.
Would it be feasible? In theory, it shouldn't be that hard, but since nimble is close source, I have no way of evaluating the energy necessary to make this possible. I'm pretty sure I'm not the only one that would like this to be possible.
Else, something that could also work is if the edge could validate if a chunk is the same on the origin and update it if it is not.
what would you propose to fix this ? The most simple way in such rare case is just to change stream name.
I see the only one effective way is to add Nimble api to clear particular item. What do you think?
Nimble API would be the perfect way to do this, if it can be implemented. Easy to automate on my side :)
OK, we'll plan implementing this functionality, thank you for the idea.
This feature is not implemented, unfortunately.
Could you please describe your use case for this feature, by launching a ticket at http://wmspanel.com/help
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the