forked from docs/doc-exports
Hasko, Vladimir
a5cc543164
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com> Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
105 lines
8.7 KiB
HTML
105 lines
8.7 KiB
HTML
<a name="ddm_04_0025"></a><a name="ddm_04_0025"></a>
|
|
|
|
<h1 class="topictitle1">What Risky Operations on RDS for MySQL Will Affect DDM?</h1>
|
|
<div id="body1526376353062"><p id="ddm_04_0025__p8060118"><a href="#ddm_04_0025__table601177597">Table 1</a> lists risky operations on RDS for MySQL.</p>
|
|
|
|
<div class="tablenoborder"><a name="ddm_04_0025__table601177597"></a><a name="table601177597"></a><table cellpadding="4" cellspacing="0" summary="" id="ddm_04_0025__table601177597" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Risky operations on RDS for MySQL</caption><thead align="left"><tr id="ddm_04_0025__row1401177599"><th align="left" class="cellrowborder" valign="top" width="16%" id="mcps1.3.2.2.4.1.1"><p id="ddm_04_0025__p14986957193519">Operation Type</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="17%" id="mcps1.3.2.2.4.1.2"><p id="ddm_04_0025__p13014718591">Operation</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="67%" id="mcps1.3.2.2.4.1.3"><p id="ddm_04_0025__p909785920">Impact of the Operation</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="ddm_04_0025__row08833351409"><td class="cellrowborder" rowspan="9" valign="top" width="16%" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p11182162193610">Operations on the RDS for MySQL console</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="17%" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p9027105912">Deleting an RDS for MySQL instance</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="67%" headers="mcps1.3.2.2.4.1.3 "><p id="ddm_04_0025__p10087115917">After an RDS for MySQL instance is deleted, all schemas and logical tables of the DDM instance associated with the RDS instance become unavailable.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row125051197127"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p5506161921217">Stopping an RDS for MySQL instance</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p1850681941211">After an RDS for MySQL instance is stopped, all schemas and logical tables of the DDM instance associated with the RDS instance become unavailable.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row503745915"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p704712599">Performing the primary/standby switchover of an RDS for MySQL instance</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p859037172217">RDS for MySQL may be intermittently interrupted during the primary/standby switchover. In addition, a small amount of data may be lost in case of long delay in primary/standby synchronization.</p>
|
|
<ul id="ddm_04_0025__ul9130101242214"><li id="ddm_04_0025__li413012128227">Creating schemas or logical tables is not allowed on DDM during the primary/standby switchover of the RDS for MySQL instance.</li><li id="ddm_04_0025__li2255121452210">After a primary/standby switchover of an RDS for MySQL instance, the RDS instance ID remains unchanged in DDM.</li></ul>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row20087195918"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p201971598">Restarting an RDS for MySQL instance</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p885815537216">The restart of an RDS for MySQL instance makes itself unavailable and will also affect the associated DDM instance.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row18016711598"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p1505717597">Resetting a password</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p10376599">After the password of an RDS for MySQL instance is reset, enter the new password on the <strong id="ddm_04_0025__b9575103533010">DB Instance Connection</strong> page when creating a DDM schema.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row01951557123318"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p71961557203312">Modifying a parameter template</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p898517264315">The following parameters are set to fixed values. If their values are modified, DDM will not function properly.</p>
|
|
<ul id="ddm_04_0025__ul1174173316314"><li id="ddm_04_0025__li11849133417312"><strong id="ddm_04_0025__b16648191417214">lower_case_table_names</strong>: Set this parameter to <strong id="ddm_04_0025__b541112314214">1</strong>, indicating that data table names and sequence names are case-insensitive.</li><li id="ddm_04_0025__li1811475132812"><strong id="ddm_04_0025__b825718112228">local_infile</strong>: Set this parameter to <strong id="ddm_04_0025__b1172118342211">ON</strong> in scale-out scenarios.</li></ul>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row12962644518"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p1984620401845">Modifying a security group</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p5846144015415">Your DDM instance cannot connect to associated RDS for MySQL instances.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row1391794002311"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p13917104052319">Modifying a VPC</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p1791716401234">The DDM instance and RDS for MySQL instance cannot communicate with each other if they are in different VPCs.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row11137121814117"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p5983141516316">Restoring data</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p129831615932">Restoring data may damage data integrity.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row4231784349"><td class="cellrowborder" rowspan="6" valign="top" width="16%" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p9987135733515">Operations through an RDS for MySQL client</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="17%" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p123114818342">Deleting a physical database created on DDM</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="67%" headers="mcps1.3.2.2.4.1.3 "><p id="ddm_04_0025__p1923113820342">After a physical database is deleted, the original data will be lost and new data cannot be written into the database.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row628211117349"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p528211114349">Deleting an account created on DDM</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p19282311173412">After an account is deleted, logical tables cannot be created on DDM.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row113203253211"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p1232017252213">Deleting a physical table created on DDM</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p11321172519219">After a physical table is deleted, data stored on DDM will be lost. The corresponding logical table becomes unavailable on DDM.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row124737268816"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p114738261289">Modifying the name of a physical table created on DDM</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p1147318261083">DDM cannot obtain data of the corresponding logical table, and the logical table becomes unavailable on DDM.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row17129211131"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p181292115310">Changing a record</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p1813012111835">Changing a record in a broadcast table will affect the data consistency of shards.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="ddm_04_0025__row1881173614310"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.1 "><p id="ddm_04_0025__p78811736333">Modifying a whitelist</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.4.1.2 "><p id="ddm_04_0025__p188812361632">A DDM instance cannot access the RDS for MySQL instance if it is not in the RDS instance whitelist.</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_04_0047.html">RDS-related Questions</a></div>
|
|
</div>
|
|
</div>
|
|
|