[
https://issues.apache.org/jira/browse/ARTEMIS-2823?focusedWorklogId=484943&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-484943
]
ASF GitHub Bot logged work on ARTEMIS-2823:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Sep/20 05:50
Start Date: 16/Sep/20 05:50
Worklog Time Spent: 10m
Work Description: franz1981 commented on pull request #3204:
URL: https://github.com/apache/activemq-artemis/pull/3204#issuecomment-693187113
@uomik
> The drawback with shared store, being database or something else, is that
it essentially becomes a single point of failure for the whole cluster. If we
lose the database, we lose the ability to sync data between master and backup,
the ability to ensure data integrity and broker high availability. In this
case, on my opinion, the only thing we can do is to shut down the broker node
as precautionary measure. This is the way it was before I fiddled with
anything, and I saw no reasons to change it.
Agree, but consider the simple case of a database upgrade ( ie a database
restart): a shared store implies a live and backup connected to it; the
expectation during a database upgrade would be that the live will go down
(that's what is happening now) while the slave should keep trying to became
live (ie while now it just die).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 484943)
Time Spent: 5h 20m (was: 5h 10m)
> Improve JDBC connection management
> ----------------------------------
>
> Key: ARTEMIS-2823
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2823
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Reporter: Mikko
> Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> I have a case where the whole clustering reliability and HA must rely on HA
> capabilities of clustered database, and running on top of application server
> is not an option.
> The current JDBC store implementation is rather bare bones on the connection
> management side. JDBC driver is used directly with no management layer. At
> startup, the broker just opens couple of direct connections to database and
> expects them to be available forever. This is something that cannot be
> expected in HA production environment. So, similarly to the discussion linked
> below, in our case we lose the db connection after one hour, and all the
> brokers need to be restared to get new connections:
> [http://activemq.2283324.n4.nabble.com/Artemis-does-not-reconnect-to-MySQL-after-connection-timeout-td4751956.html]
>
> This is something that could be resolved by simply using JDBC4 isValid
> checks, but proper connection handling and pooling through datasource would
> be preferrable.
> I have implemented a solution for this by using DBCP2 datasource. Our test
> cluster has been successfully running this forked version since the release
> of Artemis 2.13.0. I will prepare of pull request if this is seen to be
> something that can be useful.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
