Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 26 Sep 2012 06:54:07 +1100 (NCT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <39095173.124665.1348602847569.JavaMail.jiratomcat@arcas>
In-Reply-To: <417499582.118637.1348520049086.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (DERBY-5937) File handle is leaked when a Slave
 replication is shutdown with failover=true
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463152#comment-13463152 ] 

Knut Anders Hatlen commented on DERBY-5937:
-------------------------------------------

Hi Glenn,

If I understand correctly, this is what you're doing when you see the problem:

1) You have a master database that is being replicated to the slave, and you detect some kind of trouble with the master database

2) You invoke failover=true on the slave database (which completes as expected)

3) You then invoke shutdown=true on the slave database (which also completes as expected)

After these steps, the slave process is still holding log1.dat open.

Does that sound about right?

Thanks.
                
> File handle is leaked when a Slave replication is shutdown with failover=true
> -----------------------------------------------------------------------------
>
>                 Key: DERBY-5937
>                 URL: https://issues.apache.org/jira/browse/DERBY-5937
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.8.2.2
>         Environment: Windows 7
>            Reporter: Glenn McGregor
>
> As part of our use of derby replication, we shut the slave down if we detect reachability issues with the master. Normally we shut it down, and bring it back up as a regular database in read-only mode.  Then when the master can, it tries to push a fresh copy back to the slave system. However, during the failover=true shutdown on the slave, the log file  ".../name/log/log1.dat" is still open. 
> Because of this open file, at least on Windows, it's impossible to move the database file out of the way, and to install a fresh copy from the master.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira