[
https://issues.apache.org/jira/browse/KARAF-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735074#comment-16735074
]
ASF subversion and git services commented on KARAF-6037:
--------------------------------------------------------
Commit b368a87cba0f0e235d5dae72fd6c3559b50fb75c in karaf's branch
refs/heads/master from Kaja Mohideen
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=b368a87 ]
KARAF-6037 Adding support to tolerate lock lost (#710)
[KARAF-6037] Support several attempt on lock (especially for JDBC) before
shutdown of the active instance
> DB connection and acquire lock to be retried few times before giving up
> -----------------------------------------------------------------------
>
> Key: KARAF-6037
> URL: https://issues.apache.org/jira/browse/KARAF-6037
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.0.4
> Environment: Apache Karaf 4.0.4
> DB Lock using MySQLJDBCLock.
> Reporter: Kaja Mohideen
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Labels: HA,, jdbc
> Fix For: 4.2.3
>
>
> I’m trying to use Karaf HA/failover feature documented here :
> [http://karaf.apache.org/manual/latest/#_ha_failover_and_cluster]
> With database lock, I see that Karaf running with the Lock as Active instance
> is just shutting down upon losing connection with DB.
> I think, it would better if Karaf tries few times to reconnect & acquire lock
> before doing shutdown. When only one instance of karaf is running and DB
> connection fluctuates, this behavior impacts availability (needs restart from
> orchestration layer).
> Note: I'm using start level = 1 and karaf.lock.slave.block = true
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
