[
https://issues.apache.org/jira/browse/CLOUDSTACK-10399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678195#comment-16678195
]
ASF GitHub Bot commented on CLOUDSTACK-10399:
---------------------------------------------
rafaelweingartner closed pull request #17: CLOUDSTACK-10399: Added section
regarding MySQL server-id
URL: https://github.com/apache/cloudstack-documentation/pull/17
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/source/installguide/management-server/_database.rst
b/source/installguide/management-server/_database.rst
index 9ec6600..46a9f13 100644
--- a/source/installguide/management-server/_database.rst
+++ b/source/installguide/management-server/_database.rst
@@ -62,6 +62,18 @@ MySQL. See :ref:`install-database-on-separate-node`.
max_connections=350
log-bin=mysql-bin
binlog-format = 'ROW'
+
+ .. note::
+ For Ubuntu 16.04 and later, make sure you specify a ``server-id`` in
your ``.cnf`` file for binary logging. Set the ``server-id`` according
to your database setup.
+
+ .. parsed-literal::
+
+ server-id=master-01
+ innodb_rollback_on_timeout=1
+ innodb_lock_wait_timeout=600
+ max_connections=350
+ log-bin=mysql-bin
+ binlog-format = 'ROW'
.. note::
You can also create a file ``/etc/mysql/conf.d/cloudstack.cnf``
diff --git a/source/quickinstallationguide/qig.rst
b/source/quickinstallationguide/qig.rst
index a45962b..ac853b6 100644
--- a/source/quickinstallationguide/qig.rst
+++ b/source/quickinstallationguide/qig.rst
@@ -369,7 +369,19 @@ section:
innodb_lock_wait_timeout=600
max_connections=350
log-bin=mysql-bin
- binlog-format = 'ROW'
+ binlog-format = 'ROW'
+
+.. note::
+For Ubuntu 16.04 and later, make sure you specify a ``server-id`` in your
``.cnf`` file for binary logging. Set the ``server-id`` according to your
database setup.
+
+::
+
+ server-id=master-01
+ innodb_rollback_on_timeout=1
+ innodb_lock_wait_timeout=600
+ max_connections=350
+ log-bin=mysql-bin
+ binlog-format = 'ROW'
Now that MySQL is properly configured we can start it and configure it to
start on boot as follows:
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Specify MySQL server-id for later versions of CloudStack
> --------------------------------------------------------
>
> Key: CLOUDSTACK-10399
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10399
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Affects Versions: 4.11.1.0
> Environment: Ubuntu 16.04 LTS
> Reporter: James McClune
> Priority: Minor
> Labels: doc
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> I created a PR for this issue on the old CloudStack documentation:
> [https://github.com/apache/cloudstack-docs-install/pull/38]
> When looking at the new documentation, I don't think this PR was migrated
> over.
> Using Ubuntu 16.04 and MySQL 5.7.22, I found specifying a {{server-id}} is
> critical for running the MySQL process with binary logging. I updated the
> documentation to include a section about using the \{{server-id }}directive
> for MySQL version 5.7 and later.
> Pages affected:
> [http://docs.cloudstack.apache.org/en/4.11.1.0/quickinstallationguide/qig.html#management-server-installation]
> http://docs.cloudstack.apache.org/en/4.11.1.0/installguide/management-server/index.html#install-the-database-server
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
