db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Thalamati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.
Date Tue, 06 Dec 2005 18:54:09 GMT
     [ http://issues.apache.org/jira/browse/DERBY-239?page=all ]

Suresh Thalamati updated DERBY-239:

    Attachment: onlinebackup_5.diff

This pacth  fixes store/onlineBackupTest1.java failure on non-windows envirorment.   Problem
 was  unlogged operations thread and insert thread are working on the  same connection. Test
was failing becuase  insert thread  was committing the unlogged operation that was suppose
to block the backup. 
This pacth modified the test , so that  these threads works on different conenctions, 

Test passed on Windows XP and Linuix. 

It would be great  if some  one can commit this patch. 

> Need a online backup feature  that does not block update operations   when online backup
is in progress.
> --------------------------------------------------------------------------------------------------------
>          Key: DERBY-239
>          URL: http://issues.apache.org/jira/browse/DERBY-239
>      Project: Derby
>         Type: New Feature
>   Components: Store
>     Versions:
>     Reporter: Suresh Thalamati
>     Assignee: Suresh Thalamati
>  Attachments: onlinebackup.html, onlinebackup1.html, onlinebackup_1.diff, onlinebackup_2.diff,
onlinebackup_3.diff, onlinebackup_4.diff, onlinebackup_5.diff
> Currently Derby allows users to perfoms  online backups using SYSCS_UTIL.SYSCS_BACKUP_DATABASE()
procedure,  but while the backup is in progress, update operations are temporarily blocked,
but read operations can still proceed.
> Blocking update operations can be real issue specifically in client server environments,
because user requests will be blocked for a long time if a 
> backup is in the progress on the server.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message