Re: [Maria-discuss] Debian 9 support for MaxScale
Martin: Debian 9 build for MaxScale 2.1.5 is now available at https://mariadb.com/downloads/mariadb-tx/maxscale Regards, Dipti E: dipti.jo...@mariadb.com Twitter: @dipti_smg On Thu, Aug 3, 2017 at 4:43 AM, Martin Toth <snowmai...@gmail.com> wrote: > Thanks for help and answers. > > BR, > Martin > > > On 02 Aug 2017, at 17:50, Dipti Joshi <dipti.jo...@mariadb.com> wrote: > > Martin: > > Sending this to MaxScale group. We are working on it , and should have it > out soon. > > Regards, > Dipti > > > E: dipti.jo...@mariadb.com > Twitter: @dipti_smg > > On Wed, Aug 2, 2017 at 9:25 AM, Martin Toth <snowmai...@gmail.com> wrote: > >> Hi all, >> >> I would like to ask if there is some release date for fixing >> https://jira.mariadb.org/browse/MXS-1292 . Debian 9 should be included >> as a build target ASAP. >> I am installing only D9 systems on new servers and I am unable to use >> builds for MaxScale, so its unusable in D9. >> >> Thanks. >> >> Martin >> ___ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : maria-discuss@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp >> > > > -- > You received this message because you are subscribed to the Google Groups > "MaxScale" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to maxscale+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Re: [Maria-discuss] Debian 9 support for MaxScale
Martin: Sending this to MaxScale group. We are working on it , and should have it out soon. Regards, Dipti E: dipti.jo...@mariadb.com Twitter: @dipti_smg On Wed, Aug 2, 2017 at 9:25 AM, Martin Tothwrote: > Hi all, > > I would like to ask if there is some release date for fixing > https://jira.mariadb.org/browse/MXS-1292 . Debian 9 should be included as > a build target ASAP. > I am installing only D9 systems on new servers and I am unable to use > builds for MaxScale, so its unusable in D9. > > Thanks. > > Martin > ___ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss@lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Re: [Maria-discuss] MariaDB 10.0.30 now available
Karthick: As you are MariaDB subscription customer, you should raise use of latest GA version and MariaDB enterprise yum repository directly with MariaDB Support. Regards, Dipti On Wed, Mar 8, 2017 at 1:52 PM, Karthick Subramanian < ksubraman...@paycommerce.com> wrote: > Thank you for the details. I understood now why we have multiple GA > releases with different versions. My initial impression was - I need to use > the GA release of higher version when it's available. > > Also in Mariadb customer portal dashboard, "download MariaDB" always shows > latest higher version GA when I choose my OS version. So I thought that's > the superior version available for production environment. Also my YUM > update automatically choose the higher GA version of MariaDB from MariaDB > enterprise repo. > > Thank you again for the details. > > > On Mar 9, 2017, at 12:43 AM, Reindl Harald> wrote: > > > > > > > >> Am 08.03.2017 um 19:44 schrieb Karthick Subramanian: > >> Sorry if this question seems silly: > >> > >> Why we need to use 10.0.30 when we already have 10.1. Series with GA. > > > > because 10.x is still supported and the whole world don't jump and fire > out the next major version of every piece of software and hope all is fine? > > > > why do we need that many linux kernels with critical bugfixes when we > have 4.10.1? > > > > https://www.kernel.org/ > > > >> Why don't we upgrade from 10.0 series to 10.1 GA series. Is there > anything that fixed in 10.0.30 which yet to fix in 10.1.21 GA. Thank you > for helping me to understand these different version series. > > > > because nobody right in his mind blows out the next shiny major version > before tests? because that's the reason major/minor/revision exists at all > > > > because LTS distributions exists for a good reason which means you won't > see anything but MAriaDB 5.5x ever on RHEL7 > > > > ___ > > Mailing list: https://launchpad.net/~maria-discuss > > Post to : maria-discuss@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~maria-discuss > > More help : https://help.launchpad.net/ListHelp > > ___ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss@lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Re: [Maria-discuss] Reg replication and commit
Karthick: You should post this in maxscale group as well. Dipti On Fri, Oct 14, 2016 at 6:34 PM, Kristian Nielsenwrote: > Karthick Subramanian writes: > > > Below when I try at Slave DB: > > > > MariaDB [dr_repl]> select * from test_dr_repl; > > Empty set (0.00 sec) > > > > MariaDB [dr_repl]> commit; > > Query OK, 0 rows affected (0.00 sec) > > > > MariaDB [dr_repl]> select * from test_dr_repl; > > ++--+ > > | id | val | > > ++--+ > > | 1 |1 | > > | 2 |2 | > > | 3 |3 | > > ++--+ > > 3 rows in set (0.00 sec) > > I wasn't really able to fully understand your explanation of your problem. > > However, the above suggests you have an open transaction with isolation > level REPEATABLE READ. This is the only situation I can think of where a > COMMIT will affect the visibility of other rows. When you open a > transaction > with REPEATABLE READ (with BEGIN, or with autocommit off), no new changes > will be visible until COMMIT or ROLLBACK. This is a basic feature of InnoDB > transactions, independent of replication. > > - Kristian. > > ___ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss@lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Re: [Maria-discuss] Reg custom port for maxscale binlog router
Karthick: Please ask MaxScale question on maxsc...@googlegroups.com - I have cced here. The port 5308 in documentation is for listener for a mysql client that you would use as following to register MaxScale with Master as slave srvr:/home/my-usr$ mysql -u root -p 5308 -h >CHANGE MASTER TO MASTER_HOST=‘$master_server’, MASTER_PORT=$master_port, MASTER_USER='repl', MASTER_PASSWORD=‘somepasswd’, MASTER_LOG_FILE=‘repl-bin.000159', MASTER_LOG_POS=4 > START SLAVE Is that what your are doing ? Thanks, Dipti On Mon, Aug 29, 2016 at 7:11 AM, Karthick Subramanian < ksubraman...@paycommerce.com> wrote: > Hi all, > > When I try to configure maxscale for binlogrouter, I noticed that > documentation examples using port as 5308. When I try to configure > similarly, it says, 111 connection refused or unable to connect master from > maxscale. > > I have enabled the port in centOs7 using firewalld on both master server > as well maxscale server: > > firewall-cmd --add-port=5308/tcp > > But still,I couldn't able to establish connection from maxscale server to > mariadb server(master): > > mysql -u maxscaleoper -h ip:ip:ip:ip --port 5308 -p > > ERROR 2003 (HY000): Can't connect to MySQL server on 'ip:ip:ip:ip' (111 > "Connection refused") > > Can anyone please help me on how to resolve this error. Because of this > error, I couldn't make maxscale up and running. > > Regards, > Karthick S > > > ___ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss@lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Re: [Maria-discuss] Regarding DR site set-up
Karthick: Wanted to confirm what is your server configuration on DR site ? Do you expect your write queries to continue on DR site when production is down ? Regards, Dipti On Tue, Jul 5, 2016 at 8:16 AM, Dipti Joshi <dipti.jo...@mariadb.com> wrote: > Karthick, > > Also copying this conversation to maxsc...@googlegroups.com > > Based on your configuration, you should also setup your DR site similar > way as your product site, i.e. MaxScale in both locations. > > Regards, > Dipti > > On Tue, Jul 5, 2016 at 12:02 AM, Karthick Subramanian < > ksubraman...@paycommerce.com> wrote: > >> Dear Experts, >> >> I have a question on Max Scale requirement: >> >> In prod - we have two DB server as Primary(Master) and Secondary(Slave). >> Both being controlled via MaxScale. >> >> Do we need to really set it up similar way in DR site also? I meant - Do >> we need to keep Max Scale set it up in DR as well. Anyway, DR is going to >> be exceptional scenarios in which entire application servers also work out >> of DR site and we can still point all the app servers in DR site configured >> directly to access the Maria DB server at DR instead of Max Scale. >> >> Note: We are currently not using MaxScale for any complex needs, we are >> using MaxScale for normal routing like RW split etc. >> >> I know ideal is keep both Prod site and DR site equivalent. But as cost >> cutting on servers etc, shall we keep DR the way I mentioned. Could you >> please provide your opinion on this. >> >> Regards, >> Karthick >> >> ___ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : maria-discuss@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp >> >> > ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Re: [Maria-discuss] Regarding DR site set-up
Karthick, Also copying this conversation to maxsc...@googlegroups.com Based on your configuration, you should also setup your DR site similar way as your product site, i.e. MaxScale in both locations. Regards, Dipti On Tue, Jul 5, 2016 at 12:02 AM, Karthick Subramanian < ksubraman...@paycommerce.com> wrote: > Dear Experts, > > I have a question on Max Scale requirement: > > In prod - we have two DB server as Primary(Master) and Secondary(Slave). > Both being controlled via MaxScale. > > Do we need to really set it up similar way in DR site also? I meant - Do > we need to keep Max Scale set it up in DR as well. Anyway, DR is going to > be exceptional scenarios in which entire application servers also work out > of DR site and we can still point all the app servers in DR site configured > directly to access the Maria DB server at DR instead of Max Scale. > > Note: We are currently not using MaxScale for any complex needs, we are > using MaxScale for normal routing like RW split etc. > > I know ideal is keep both Prod site and DR site equivalent. But as cost > cutting on servers etc, shall we keep DR the way I mentioned. Could you > please provide your opinion on this. > > Regards, > Karthick > > ___ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss@lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp