You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Paul Querna (JIRA)" <ji...@apache.org> on 2009/10/03 21:57:23 UTC
[jira] Created: (INFRA-2261) Intermitent Failues when a commit is
going on
Intermitent Failues when a commit is going on
---------------------------------------------
Key: INFRA-2261
URL: https://issues.apache.org/jira/browse/INFRA-2261
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Components: Subversion
Reporter: Paul Querna
Subversion sometimes gives an error when a commit is on going.
Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem.
On the server side, the following is logged:
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
The string 'database is locked' appears to come from SQLite:
SQLITE_BUSY: z = "database is locked";
I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2261) Intermitent Failues when a commit is
going on
Posted by "Paul Querna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Querna updated INFRA-2261:
-------------------------------
Description:
Subversion sometimes gives an error when a commit is on going.
Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem. (Using fsfs, SVN 1.6.6)
On the server side, the following is logged:
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
The string 'database is locked' appears to come from SQLite:
SQLITE_BUSY: z = "database is locked";
I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
fsfs repo
was:
Subversion sometimes gives an error when a commit is on going.
Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem.
On the server side, the following is logged:
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
[Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
The string 'database is locked' appears to come from SQLite:
SQLITE_BUSY: z = "database is locked";
I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
> Intermitent Failues when a commit is going on
> ---------------------------------------------
>
> Key: INFRA-2261
> URL: https://issues.apache.org/jira/browse/INFRA-2261
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Paul Querna
>
> Subversion sometimes gives an error when a commit is on going.
> Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem. (Using fsfs, SVN 1.6.6)
> On the server side, the following is logged:
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> The string 'database is locked' appears to come from SQLite:
> SQLITE_BUSY: z = "database is locked";
> I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
> Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
> When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
> fsfs repo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2261) Intermitent Failues when a commit is
going on
Posted by "Richard England (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851150#action_12851150 ]
Richard England commented on INFRA-2261:
----------------------------------------
I believe I have encountered this problem with a user using "svn import" to pull in a cvs exported repo. Is there any indication when this issue might be addressed? It sounds like there are some possible solutions that have been discussed.
Are there any viable workarounds?
> Intermitent Failues when a commit is going on
> ---------------------------------------------
>
> Key: INFRA-2261
> URL: https://issues.apache.org/jira/browse/INFRA-2261
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Paul Querna
>
> Subversion sometimes gives an error when a commit is on going.
> Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem. (Using fsfs, SVN 1.6.6)
> On the server side, the following is logged:
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> The string 'database is locked' appears to come from SQLite:
> SQLITE_BUSY: z = "database is locked";
> I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
> Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
> When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
> fsfs repo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2261) Intermitent Failues when a commit is
going on
Posted by "C. Michael Pilato (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857475#action_12857475 ]
C. Michael Pilato commented on INFRA-2261:
------------------------------------------
I wonder if, until the bug is fixed, disabling rep sharing in the fsfs.conf file would help?
> Intermitent Failues when a commit is going on
> ---------------------------------------------
>
> Key: INFRA-2261
> URL: https://issues.apache.org/jira/browse/INFRA-2261
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Paul Querna
>
> Subversion sometimes gives an error when a commit is on going.
> Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem. (Using fsfs, SVN 1.6.6)
> On the server side, the following is logged:
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> The string 'database is locked' appears to come from SQLite:
> SQLITE_BUSY: z = "database is locked";
> I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
> Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
> When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
> fsfs repo
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-2261) Intermitent Failues when a commit is
going on
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905588#action_12905588 ]
#asfinfra IRC Bot commented on INFRA-2261:
------------------------------------------
<danielsh> possibly happened again now (with 1.6.12 server): http://thread.gmane.org/gmane.comp.version-control.subversion.devel/122328
> Intermitent Failues when a commit is going on
> ---------------------------------------------
>
> Key: INFRA-2261
> URL: https://issues.apache.org/jira/browse/INFRA-2261
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Paul Querna
>
> Subversion sometimes gives an error when a commit is on going.
> Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem. (Using fsfs, SVN 1.6.6)
> On the server side, the following is logged:
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> The string 'database is locked' appears to come from SQLite:
> SQLITE_BUSY: z = "database is locked";
> I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
> Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
> When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
> fsfs repo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2261) Intermitent Failues when a commit is
going on
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882992#action_12882992 ]
#asfinfra IRC Bot commented on INFRA-2261:
------------------------------------------
<pgollucc1> subversion now at 1.6.12 on asf infra
> Intermitent Failues when a commit is going on
> ---------------------------------------------
>
> Key: INFRA-2261
> URL: https://issues.apache.org/jira/browse/INFRA-2261
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Paul Querna
>
> Subversion sometimes gives an error when a commit is on going.
> Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem. (Using fsfs, SVN 1.6.6)
> On the server side, the following is logged:
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> The string 'database is locked' appears to come from SQLite:
> SQLITE_BUSY: z = "database is locked";
> I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
> Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
> When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
> fsfs repo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2261) Intermitent Failues when a commit is
going on
Posted by "Daniel Shahaf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879883#action_12879883 ]
Daniel Shahaf commented on INFRA-2261:
--------------------------------------
Patches concerning the aforementioned issue (aka svn issue #3506) have been now been backported and should be availble in Subversion 1.6.12 (which is to be released soon).
> Intermitent Failues when a commit is going on
> ---------------------------------------------
>
> Key: INFRA-2261
> URL: https://issues.apache.org/jira/browse/INFRA-2261
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Paul Querna
>
> Subversion sometimes gives an error when a commit is on going.
> Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem. (Using fsfs, SVN 1.6.6)
> On the server side, the following is logged:
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> The string 'database is locked' appears to come from SQLite:
> SQLITE_BUSY: z = "database is locked";
> I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
> Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
> When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
> fsfs repo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-2261) Intermitent Failues when a commit is
going on
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot closed INFRA-2261.
------------------------------------
Resolution: Fixed
> Intermitent Failues when a commit is going on
> ---------------------------------------------
>
> Key: INFRA-2261
> URL: https://issues.apache.org/jira/browse/INFRA-2261
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Paul Querna
>
> Subversion sometimes gives an error when a commit is on going.
> Clients that are just connecting to svn will get a failure about being unable to open the SVN filesystem. (Using fsfs, SVN 1.6.6)
> On the server side, the following is logged:
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] (20014)Internal error: database is locked
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not fetch resource information. [500, #0]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> [Sat Oct 03 16:20:14 2009] [error] [client 140.211.11.140] Could not open the requested SVN filesystem [500, #200030]
> The string 'database is locked' appears to come from SQLite:
> SQLITE_BUSY: z = "database is locked";
> I believe this might be due to the size of our rep-cache.db. On eris, it is now about 500mb and growing.
> Looking at our older error logs, we seem to hit this about once a week. It seems to be directly related to large commits, with hundreds or thousands of files.
> When this is happening, for a period of 5-20 seconds, any clients connecting to svn.apache.org will receive a message that the server is unable to open the filesystem.
> fsfs repo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.