You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2019/01/06 05:12:00 UTC
[jira] [Updated] (KARAF-6037) DB connection and acquire lock to be
retried few times before giving up
[ https://issues.apache.org/jira/browse/KARAF-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-6037:
----------------------------------------
Labels: HA, jdbc (was: )
> 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)