Thoughts on commit via the out-dated(by irrelevant revisions i.e just by number) mirror
From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: Mon, 04 Jan 2010 19:18:45 +0530
Hi All,
Reposting http://mail-archives.apache.org/mod_mbox/subversion-dev/200912.mbox/browser for easy context with recent findings.
Of late we have observed errors like the following when committing via
<snip>
"The specified baseline is not the latest baseline, so it may not be checked
This error happens as the following request part of the commit operation is *served by mirror*.
We can proxy this request to the Master but we *should not* do that if it is for read operation.
There are couple of ways to identify whether a request is a read request or write.
Approach 1:
Drawback: There could be old clients which can make each request in its own connection and hence would suffer from the above issue.
Approach 2:
Drawback: This most probably happen only on svn 1.7.x so still old clients would suffer from the above issue.
I have Patch for both the approaches in my WC.
Some of my observations with my patch for Approach2:
Combo2:
As Approach 1 and Approach 2 can co-live, I will post the patch soon after cleaning it up.
So with this collective approach only 'one request/one connection' client(by the way which version of svn or neon is that?) has to suffer.
Thanks
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.