[svk-devel] Problem syncing mirror

Jason Dillon jason at planet57.com
Mon Feb 12 08:11:25 EST 2007


Many thanks!  I actually did not realize that we were still using 1.3  
on svn.apache.org... gotta see when thats going to change.

Once the server is 1.4 would you expect that `svk sync` would work  
better on large revisions and not fail with 'RA layer request  
failed...' fluff?

--jason


On Feb 12, 2007, at 4:52 AM, Chia-Liang Kao wrote:

> Hi Jason,
>
> svk 2 does have make use of the new api found in 1.4 whenever it's
> available on both client and server.  So as soon as svn.apache.org
> upgrades to 1.4 on the server side, you should be able to sync from
> it.  HTH.
>
> Cheers,
> CLK
>
>
> On 11/02/07, Jason Dillon <jason at planet57.com> wrote:
>> When asking for status about the dump again from ASF infra William A.
>> Rowe, Jr. <wrowe at rowe-clan.net>, mentioned something about new SVN
>> sync features in 1.4 which might help solve this problem:
>>
>> On Feb 10, 2007, at 8:21 AM, William A. Rowe, Jr. wrote:
>> > Jason Dillon wrote:
>> >> Is there a new API or is it just the new svnsync binary?
>> >
>> > From 1.4 new features, svnsync entry notes...
>> >
>> > """
>> > A new tool — svnsync — is now installed as part of the standard
>> > distribution.
>> > This tool provides the ability to replicate history from one
>> > repository to
>> > another. The replication can happen all at once, or can be done
>> > incrementally
>> > through repeated 'sync' operations. Because the tool uses the
>> > abstract network
>> > (RA) API, the source and destination repositories can be either
>> > local, remote,
>> > or any combination thereof.
>> >
>> > Compatibility note: in order to "push" information into a  
>> destination
>> > repository, any version of the server will suffice. The pushing is
>> > done through
>> > ordinary network commits. To "pull" history from the source
>> > repository, however,
>> > requires a 1.4 (or later) server.
>> > """
>> >
>> > So it's both, the RA API, and the ability do do smaller syncs which
>> > would solve
>> > the issue you have today with svk.  I'm certain there would be
>> > porting work for
>> > the svk authors to pick up the RA API.
>>
>> It would really be helpful if SVK could handle sync'ing repos with
>> large revisions better.  Perhaps using the new 1.4 sync support in
>> SVN might be more efficient/friendly on the httpd and it won't kill
>> the connection too?
>>
>> Can anyone confirm there are new sync API's in SVN 1.4 which can be
>> used by SVK to get more efficient mirror syncing?
> _______________________________________________
> svk-devel mailing list
> svk-devel at bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel



More information about the svk-devel mailing list