On Wed, Jun 10, 2015 at 8:01 PM, Shawn Heisey wrote:
> On 6/10/2015 12:49 AM, Shalin Shekhar Mangar wrote:
> > When the actual transfer of a file starts, then the whole commit point
> > is "saved" i.e. it won't be released until the entire file transfer is
> > complete (this is different from a "
On 6/10/2015 12:49 AM, Shalin Shekhar Mangar wrote:
> When the actual transfer of a file starts, then the whole commit point
> is "saved" i.e. it won't be released until the entire file transfer is
> complete (this is different from a "reserve" which is time based). At
> the end of the transfer of
Comments inline:
On Wed, Jun 10, 2015 at 11:45 AM, Shawn Heisey wrote:
> On 6/9/2015 10:46 PM, Shalin Shekhar Mangar wrote:
> > That comment about commitReserveDuration is not accurate. It has nothing
> > to do with the size of the index. It is the time for which commits are
> > reserved even if
On 6/9/2015 10:46 PM, Shalin Shekhar Mangar wrote:
> That comment about commitReserveDuration is not accurate. It has nothing
> to do with the size of the index. It is the time for which commits are
> reserved even if no request has accessed them. A commit and its related
> files will never be dele
Hi Shawn,
That comment about commitReserveDuration is not accurate. It has nothing to
do with the size of the index. It is the time for which commits are
reserved even if no request has accessed them. A commit and its related
files will never be deleted as long as a request is fetching them. The o
