karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-6037) DB connection and acquire lock to be retried few times before giving up
Date Fri, 04 Jan 2019 16:29:00 GMT

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

ASF GitHub Bot commented on KARAF-6037:
---------------------------------------

kaja-mohideen commented on pull request #710: KARAF-6037 Adding support to tolerate lock lost
URL: https://github.com/apache/karaf/pull/710
 
 
   Adding a new configuration to tolerate lock lost for surviving DB connectivity fluctuations.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>
> 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)

Mime
View raw message