[
https://issues.apache.org/jira/browse/DERBY-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463210#comment-13463210
]
Glenn McGregor commented on DERBY-5937:
---------------------------------------
1. Close enough. The master database is embedded in a JVM that is pinged using
an RMI call and some timers. When that fails, the switchover is attempted.
2. Yes.
2.5 I change the database property defaultConnectionMode to readOnlyAccess.
The database is left up (in readonly mode) for use until the master is
reachable again.
... time passes
3. The master detects it can talk to the slave JVM, and does a shutdown=true on
the slave database. It succeeds.
4. Many additional steps to get it back into master/slave replication.
> 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
> Labels: derby_triage10_10
>
> 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
