Announcement

Collapse
No announcement yet.

Separate MySQL server and CL / db_governor

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Separate MySQL server and CL / db_governor

    First of all I didn try it so I was wondering if anyone is using separate server for mysql if it really worth it.
    (the "Setup Remote Mysql Server" in WHM) using cloudlinux in front cpanel server.

    And if it worth it (faster loading, less cpu, more accounts on the same servers etc), can db governor work
    in the separate mysqld system (cloudlinux on the mysql server) ?

  • #2
    Christos,
    DB governor will work with separate MySQL system, but CL has to be installed on that system (CL kernel needed for throttling to be possible).

    I cannot comment on having remote MySQL server -- it depends on quite a few things, and I seen companies running MySQL both ways with quite good results.

    Comment


    • #3
      Im thinking about the following config:
      3 DA servers with Cloudlinux + 1 remote MySQL server

      All 3 DirectAdmin servers will use the same MySQL server. I was using such config without CL installed in the past but will db_governor work in such configuration where db_governor on all 3 servers checks one MySQL server. I don know exactly how db_governor works and am affaid whether db_governor from one DA server will not interfere with another one.

      Comment


      • #4
        You would need to install governor on MySQL server only. It has to reside on the same server as MySQL

        Comment


        • #5
          If I install governor on MySQL server only then how will it restrict the users on DA server to LVE id 3?

          Or you mean I should install the plugin on the MySQL server and the db_governor service on the DA server? But then the db_governor service could interfere if run in parallel on different DA servers.

          Comment


          • #6
            MySQL governor should be installed on the same server as MySQL server.
            You can control settings for LVE 3 using command line interface.

            Comment


            • #7
              When db_governor is running on MySQL server and it decides to restrict user "abc" it will try to put "abc" user into LVE 3 on MySQL server but .... the user doesn exist on DB server but on DirectAdmin server.

              Comment


              • #8
                LVE #3 is a MySQL Abusers LVE -- where all abusers will be placed. It doesn matter if MySQL server is on another machine. It has no relationship to system user.

                Comment

                Working...
                X