You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Gleason, Todd" <tg...@impac.com> on 2008/11/12 16:26:50 UTC
Commit failures on large commits
We're seeing failures a lot of the time (but not always) when we try to
commit large amounts of data (this is an initial import with several
hundred MB and over 20000 files). Here is a recent example:
svn: Commit failed (details follow):
svn: Server sent unexpected return value (401 Authorization Required) in
response to PUT request for '/eng/[repo
name]/!svn/wrk/ce3b1242-8c86-c340-ab31-857105e2e732/[some path/file]'
We're using NTLM with SSL cache timeout at 40,000 and
Maxkeepaliverequests 0 (infinite). Prior to these settings we were
seeing errors more like this:
svn: Commit failed (details follow):
svn: MKCOL of '/eng2/[repo
name]/!svn/wrk/cb9d7151-437a-da41-b995-681352de7321/[some path] ':
authorization failed (https://[server name])
I don't know whether these are essentially the same or different. We
have also enabled basic authentication (I believe it's SSPIOfferBasic
On). Some of this is due to our network environment here, but some of
it based on things I read at
http://www.nabble.com/SSPI-reauthentication-during-commit-fails-it-td973
2674.html#a9868837 and
http://www.nabble.com/TortoiseSVN,-HTTPS,-SSPI-combination-causes-(401-A
uthorization-Required)-errors-on-large-volume-repository-modifications-t
d15439239.html . It sounds like some of the problems may be with the
neon Http library, but we're using 1.5.2 (CollabNet client under
Windows). The server is 1.5.2 running Apache 2.2 under Windows as well.
We have also seen problems when trying to move multiple
directories/files using the TortoiseSVN 1.5.3 repo-browser, but it
appears to us as though one of the above settings may have resolved this
issue. We're not sure if these two problems are related or not.
Note that most other operations seem to be working fine.
Has anyone seen similar problems, or know what to try to make this more
stable?
--Todd
Caching with TortoiseSVN
Posted by Talkov Roger <Ro...@uc4.com>.
When we first brought up a 1.5 repository for testing, I did some merges
from our exisitng repository into the 1.5 test repository. I was seeing
inaccurate logs until I turned off the caching. This was with 1.5.0.
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2008c@ryandesign.com]
Sent: Thursday, November 13, 2008 1:29 PM
To: Gleason, Todd
Cc: Subversion Users
Subject: Re: Commit failures on large commits
On Nov 13, 2008, at 09:38, Gleason, Todd wrote:
> I'm not at all worried about svn log. Everyone will be making use of
> TortoiseSVN log caching anyway.
I remember someone reporting this issue on this list recently, and
they were using TortoiseSVN. But I don't know if they were using the
caching feature.
> Besides, we're running the import using
> a script, and it's a lot easier if it simply fails the entire thing
> atomically than if we might have to resume it partway through.
Sounds reasonable.
> Are there other issues with large commits? Say I'm importing a lot of
> data while someone is doing a checkout, or copying, in another part of
> the repo. We think we're seeing more failures when this sort of thing
> is going on during an import.
Other simultaneous operations should not affect your import.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
This email (including any attachments) may contain information which is privileged, confidential, or protected. If you are not the intended recipient, note that any disclosure, copying, distribution, or use of the contents of this message and attached files is prohibited. If you have received this email in error, please notify the sender and delete this email and any attached files.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commit failures on large commits
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 13, 2008, at 09:38, Gleason, Todd wrote:
> I'm not at all worried about svn log. Everyone will be making use of
> TortoiseSVN log caching anyway.
I remember someone reporting this issue on this list recently, and
they were using TortoiseSVN. But I don't know if they were using the
caching feature.
> Besides, we're running the import using
> a script, and it's a lot easier if it simply fails the entire thing
> atomically than if we might have to resume it partway through.
Sounds reasonable.
> Are there other issues with large commits? Say I'm importing a lot of
> data while someone is doing a checkout, or copying, in another part of
> the repo. We think we're seeing more failures when this sort of thing
> is going on during an import.
Other simultaneous operations should not affect your import.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Commit failures on large commits
Posted by "Gleason, Todd" <tg...@impac.com>.
I'm not at all worried about svn log. Everyone will be making use of
TortoiseSVN log caching anyway. Besides, we're running the import using
a script, and it's a lot easier if it simply fails the entire thing
atomically than if we might have to resume it partway through.
Are there other issues with large commits? Say I'm importing a lot of
data while someone is doing a checkout, or copying, in another part of
the repo. We think we're seeing more failures when this sort of thing
is going on during an import.
--Todd
> -----Original Message-----
> From: Ryan Schmidt [mailto:subversion-2008c@ryandesign.com]
> Sent: Wednesday, November 12, 2008 11:11 PM
> To: Gleason, Todd
> Cc: users@subversion.tigris.org
> Subject: Re: Commit failures on large commits
>
>
> On Nov 12, 2008, at 10:26, Gleason, Todd wrote:
>
> > We're seeing failures a lot of the time (but not always) when we
> > try to commit large amounts of data (this is an initial import with
> > several hundred MB and over 20000 files). Here is a recent example:
> >
> > svn: Commit failed (details follow):
> > svn: Server sent unexpected return value (401 Authorization
> > Required) in response to PUT request for '/eng/[repo name]/!svn/wrk/
> > ce3b1242-8c86-c340-ab31-857105e2e732/[some path/file]'
> >
> > We're using NTLM with SSL cache timeout at 40,000 and
> > Maxkeepaliverequests 0 (infinite). Prior to these settings we were
> > seeing errors more like this:
> >
> > svn: Commit failed (details follow):
> > svn: MKCOL of '/eng2/[repo name]/!svn/wrk/cb9d7151-437a-da41-
> > b995-681352de7321/[some path] ': authorization failed (https://
> > [server name])
> >
> > I don't know whether these are essentially the same or different.
> > We have also enabled basic authentication (I believe it's
> > SSPIOfferBasic On). Some of this is due to our network environment
> > here, but some of it based on things I read athttp://www.nabble.com/
> > SSPI-reauthentication-during-commit-fails-it-
> > td9732674.html#a9868837 andhttp://www.nabble.com/TortoiseSVN,-
> > HTTPS,-SSPI-combination-causes-(401-Authorization-Required)-errors-
> > on-large-volume-repository-modifications-td15439239.html . It
> > sounds like some of the problems may be with the neon Http library,
> > but we're using 1.5.2 (CollabNet client under Windows). The server
> > is 1.5.2 running Apache 2.2 under Windows as well.
> >
> > We have also seen problems when trying to move multiple directories/
> > files using the TortoiseSVN 1.5.3 repo-browser, but it appears to
> > us as though one of the above settings may have resolved this
> > issue. We're not sure if these two problems are related or not.
> >
> > Note that most other operations seem to be working fine.
> >
> > Has anyone seen similar problems, or know what to try to make this
> > more stable?
>
> I don't know why you're running into that problem, but I wanted to
> point out that there are other issues with having enormous commits
> like this, such as anytime this initial revision is shown by "svn
> log" it will take a long time. It might be better to break up your
> initial import into several revisions (several imports). If you're
> importing multiple projects, import each project separately. Or if
> it's one large project, maybe import each folder separately. That may
> coincidentally also avoid the problem you're having now.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commit failures on large commits
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 12, 2008, at 10:26, Gleason, Todd wrote:
> We’re seeing failures a lot of the time (but not always) when we
> try to commit large amounts of data (this is an initial import with
> several hundred MB and over 20000 files). Here is a recent example:
>
> svn: Commit failed (details follow):
> svn: Server sent unexpected return value (401 Authorization
> Required) in response to PUT request for '/eng/[repo name]/!svn/wrk/
> ce3b1242-8c86-c340-ab31-857105e2e732/[some path/file]'
>
> We’re using NTLM with SSL cache timeout at 40,000 and
> Maxkeepaliverequests 0 (infinite). Prior to these settings we were
> seeing errors more like this:
>
> svn: Commit failed (details follow):
> svn: MKCOL of '/eng2/[repo name]/!svn/wrk/cb9d7151-437a-da41-
> b995-681352de7321/[some path] ': authorization failed (https://
> [server name])
>
> I don’t know whether these are essentially the same or different.
> We have also enabled basic authentication (I believe it’s
> SSPIOfferBasic On). Some of this is due to our network environment
> here, but some of it based on things I read athttp://www.nabble.com/
> SSPI-reauthentication-during-commit-fails-it-
> td9732674.html#a9868837 andhttp://www.nabble.com/TortoiseSVN,-
> HTTPS,-SSPI-combination-causes-(401-Authorization-Required)-errors-
> on-large-volume-repository-modifications-td15439239.html . It
> sounds like some of the problems may be with the neon Http library,
> but we’re using 1.5.2 (CollabNet client under Windows). The server
> is 1.5.2 running Apache 2.2 under Windows as well.
>
> We have also seen problems when trying to move multiple directories/
> files using the TortoiseSVN 1.5.3 repo-browser, but it appears to
> us as though one of the above settings may have resolved this
> issue. We’re not sure if these two problems are related or not.
>
> Note that most other operations seem to be working fine.
>
> Has anyone seen similar problems, or know what to try to make this
> more stable?
I don't know why you're running into that problem, but I wanted to
point out that there are other issues with having enormous commits
like this, such as anytime this initial revision is shown by "svn
log" it will take a long time. It might be better to break up your
initial import into several revisions (several imports). If you're
importing multiple projects, import each project separately. Or if
it's one large project, maybe import each folder separately. That may
coincidentally also avoid the problem you're having now.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org