[
https://issues.apache.org/jira/browse/KARAF-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476188#comment-17476188
]
Benjamin BONNET edited comment on KARAF-7353 at 1/14/22, 3:04 PM:
------------------------------------------------------------------
level definitions found in config.properties :
org.osgi.framework.startlevel.beginning=100
karaf.startlevel.bundle=80
felix.fileinstall.log.level = 3
system.properties does not define level, but here is our H/A lock configuration
:
karaf.lock=true
karaf.lock.class=org.apache.karaf.main.lock.PostgreSQLJDBCLock
karaf.lock.jdbc.url=jdbc:postgresql://server1:5432,server2:5432/app_db?targetServerType=primary
karaf.lock.jdbc.driver=org.postgresql.Driver
karaf.lock.jdbc.user=yyyyyyyyy
karaf.lock.jdbc.password=xxxxxxx
karaf.lock.jdbc.table=KARAF_LOCK
karaf.lock.jdbc.clustername=karaf
karaf.lock.jdbc.timeout=0
was (Author: bbonnet):
level definitions found in config.properties returns :
org.osgi.framework.startlevel.beginning=100
karaf.startlevel.bundle=80
felix.fileinstall.log.level = 3
system.properties does not define level, but here is our H/A lock configuration
:
karaf.lock=true
karaf.lock.class=org.apache.karaf.main.lock.PostgreSQLJDBCLock
karaf.lock.jdbc.url=jdbc:postgresql://server1:5432,server2:5432/app_db?targetServerType=primary
karaf.lock.jdbc.driver=org.postgresql.Driver
karaf.lock.jdbc.user=yyyyyyyyy
karaf.lock.jdbc.password=xxxxxxx
karaf.lock.jdbc.table=KARAF_LOCK
karaf.lock.jdbc.clustername=karaf
karaf.lock.jdbc.timeout=0
> JDBC Lock Long Running Transaction and PostgreSQL Vacuum
> --------------------------------------------------------
>
> Key: KARAF-7353
> URL: https://issues.apache.org/jira/browse/KARAF-7353
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.3.5
> Environment: Karaf 4.3.2 (same code as 4.3.5 and master as far as
> PostgreSQLJDBCLock is concerned)
> PostgreSQL 10
> Reporter: Benjamin BONNET
> Assignee: Jean-Baptiste Onofré
> Priority: Critical
>
> Hi,
>
> Karaf H/A relies on long running transactions (see PostgreSQLJDBCLockJDBCLock
> implementation), each Karaf instance running its own transaction to keep
> (master) or try to grab (slaves) the lock. The presence of those transactions
> prevents PostgreSQL vacuum to do its jobs correctly, and vacuum job generates
> those logs :
> {{WARNING: oldest xmin is far in the past
> HINT: Close open transactions soon to avoid wraparound problems.}}
> So, letting our Karaf instances run will lead to a TXID exhaustion.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
