<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [resolved] TAC High Availability + MariaDB failover JDBC connection in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/resolved-TAC-High-Availability-MariaDB-failover-JDBC-connection/m-p/2375240#M146975</link>
    <description>Solution: download more current client and deployed to: 
&lt;BR /&gt; 
&lt;PRE&gt;./tac/apache-tomcat/webapps/org.talend.administrator/WEB-INF/lib/mariadb-java-client-1.1.7.jar&lt;/PRE&gt; 
&lt;BR /&gt;Restarted TAC servers, checked job execution, then updated TAC database URL with: 
&lt;BR /&gt; 
&lt;PRE&gt;jdbc:mariadb:sequential://mariahost01:3306,mariahost02:3306/talend_administrator&lt;/PRE&gt; 
&lt;BR /&gt;Passed check, saved it, checked job execution, and things appear to be working as expected. Next step will be to fail the first database host, but will let things run for a day or so to make sure we are stable with the new client. 
&lt;BR /&gt;@Talend - please consider shipping with a more recent MariaDB driver so that HA users can take advantage of the failover capabilities.</description>
    <pubDate>Wed, 14 Sep 2016 18:14:55 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2016-09-14T18:14:55Z</dc:date>
    <item>
      <title>[resolved] TAC High Availability + MariaDB failover JDBC connection</title>
      <link>https://community.qlik.com/t5/Talend-Studio/resolved-TAC-High-Availability-MariaDB-failover-JDBC-connection/m-p/2375238#M146973</link>
      <description>Hello, 
&lt;BR /&gt;We have TAC (v6.1.1) up and running on dual servers, shared storage, commandline/jobservers on both, and we are running a master-master setup on MariaDB. When initially deploying TAC we simply pointed TAC to mariahost01 to ensure everything was working. Current connection URL: 
&lt;BR /&gt; 
&lt;PRE&gt;jdbc:mariadb://mariahost01:3306/talend_administrator&lt;/PRE&gt; 
&lt;BR /&gt;The challenge we're facing now is that if mariahost01 goes down, there is nothing in place to reconnect to mariahost02. According to the MariaDB docs, the JDBC driver is capable of accepting failover parameters ( 
&lt;A href="https://mariadb.com/kb/en/mariadb/about-mariadb-connector-j/#failover-parameters" target="_blank" rel="nofollow noopener noreferrer"&gt;https://mariadb.com/kb/en/mariadb/about-mariadb-connector-j/#failover-parameters&lt;/A&gt;) but when using something like this 
&lt;BR /&gt; 
&lt;PRE&gt;jdbc:mariadb:sequential://mariahost01:3306,mariahost02:3306/talend_administrator&lt;/PRE&gt; 
&lt;BR /&gt;in the URL string we get "Driver cannot understand url" error and fails the check.&amp;nbsp; 
&lt;BR /&gt;Questions: 
&lt;BR /&gt; 
&lt;BR /&gt;has anyone successfully got this working? Or is there a better solution for this? 
&lt;BR /&gt;what version of the MariaDB JDBC driver ships with TAC 6.1.1? 
&lt;BR /&gt; 
&lt;BR /&gt;Appreciate the help, 
&lt;BR /&gt;T.</description>
      <pubDate>Sat, 16 Nov 2024 10:23:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/resolved-TAC-High-Availability-MariaDB-failover-JDBC-connection/m-p/2375238#M146973</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T10:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: [resolved] TAC High Availability + MariaDB failover JDBC connection</title>
      <link>https://community.qlik.com/t5/Talend-Studio/resolved-TAC-High-Availability-MariaDB-failover-JDBC-connection/m-p/2375239#M146974</link>
      <description>Found the answer to the second question (which is always the way after you post in the forums, am I right?): 
&lt;BR /&gt; 
&lt;PRE&gt;./tac/apache-tomcat/webapps/org.talend.administrator/WEB-INF/lib/mariadb-java-client-1.1.7.jar&lt;/PRE&gt; 
&lt;BR /&gt;MariaDB docs: sequential ... since 1.3.0 
&lt;BR /&gt;MariaDB current stable release: 1.5.2 
&lt;BR /&gt;*sigh* 
&lt;BR /&gt;@Talend - any chance this has been updated in an upcoming release or am I on my own in terms of trial &amp;amp; error? The HA documentation for TAC is terrible at best so any guidance on how to actually make it HA would be most welcome.</description>
      <pubDate>Wed, 14 Sep 2016 16:01:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/resolved-TAC-High-Availability-MariaDB-failover-JDBC-connection/m-p/2375239#M146974</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-09-14T16:01:20Z</dc:date>
    </item>
    <item>
      <title>Re: [resolved] TAC High Availability + MariaDB failover JDBC connection</title>
      <link>https://community.qlik.com/t5/Talend-Studio/resolved-TAC-High-Availability-MariaDB-failover-JDBC-connection/m-p/2375240#M146975</link>
      <description>Solution: download more current client and deployed to: 
&lt;BR /&gt; 
&lt;PRE&gt;./tac/apache-tomcat/webapps/org.talend.administrator/WEB-INF/lib/mariadb-java-client-1.1.7.jar&lt;/PRE&gt; 
&lt;BR /&gt;Restarted TAC servers, checked job execution, then updated TAC database URL with: 
&lt;BR /&gt; 
&lt;PRE&gt;jdbc:mariadb:sequential://mariahost01:3306,mariahost02:3306/talend_administrator&lt;/PRE&gt; 
&lt;BR /&gt;Passed check, saved it, checked job execution, and things appear to be working as expected. Next step will be to fail the first database host, but will let things run for a day or so to make sure we are stable with the new client. 
&lt;BR /&gt;@Talend - please consider shipping with a more recent MariaDB driver so that HA users can take advantage of the failover capabilities.</description>
      <pubDate>Wed, 14 Sep 2016 18:14:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/resolved-TAC-High-Availability-MariaDB-failover-JDBC-connection/m-p/2375240#M146975</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-09-14T18:14:55Z</dc:date>
    </item>
  </channel>
</rss>

