Had asked this on github and got this response which helped
The short answer is yes, you can do this, with some important caveats.
bufferBehind is for how we manage what's in kept in buffer once the playhead moves past. But this is different from what you want. You really want to override the DASH attribute called timeShiftBufferDepth, which defines how wide the availability window is.
The availability window says effectively "this is how much content is on the server that you can request at any time." You can override this with manifest.availabilityWindowOverride:
player.configure('manifest.availabilityWindowOverride', 900);
This will ignore the timeShiftBufferDepth of the manifest and use a value of 900 seconds (15 minutes) instead. The seek range in the player will become 900 seconds.
However, if the server does not actually keep that much content around, requests for content from 900 seconds ago will result in an HTTP 404 error, and playback will stall at that position. So you can't use this to control the server's behavior in any way, or to make content available that isn't.
When we run live streams (using Shaka Streamer), only a couple of segments are kept outside the availability window. As we upload new segments to cloud storage, we also delete older ones.
So increasing the size of the availability window in the player would not work in the case of our content. Depending on the encoder/packager you're using, you may be able to increase the window size and get away with it.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…