Create a Store component

The OPS & Monitoring module of OceanBase Migration Service (OMS) Community Edition allows you to create a Store on the Store page.

Background

The Store component reads raw data from the source instance, then parses, filters, and formats the data, and finally persists the data on the local server. We recommend that you create a Store in load balancing or other scenarios where data needs to be pulled. We recommend that you create a Store in load balancing or other scenarios where data needs to be pulled.

• When the database logs still exist, the data generated a few days ago needs to be pulled.

  In this case, the current Store for the data has expired, and restarting the current Store may delay all downstream nodes. You need to create a Store starting from a timestamp.

• Load balancing is required for a subtopic. The subtopic can be a cluster-, tenant-, or database-level data source.

  This aims to prevent excessive downstream nodes from consuming the Store resources, thus ensuring stability and reducing latency.

Procedure

1. Log in to the OMS Community Edition console.

2. In the left-side navigation pane, choose OPS & Monitoring > Component. The Store tab automatically appears.

3. On the Store tab, click Add in the upper-right corner.

4. In the Add dialog box, configure the parameters.

   Parameter	Required	Description
   Subtopic	Yes	A cluster- or tenant-level data source. Select a subtopic based on the specific task. The subtopic is displayed between the two colons in the store component ID on the View Component Monitoring dialog box of the task details page.
   Node	No	The server on which the Store is started. In standalone mode, only one server is deployed, and the Store is created on that server by default. When no node is specified in high availability scenarios, the system automatically schedules the Store to a server that has not experienced any performance bottleneck.
   Timestamp	Yes	The point in time from which the Store is started. Make sure that the database logs exist. Otherwise, the Store may fail to start.

   Here is an example of how to check whether database logs exist:

   • For a MySQL database, you can use the mysqlbinlog tool to view the binlog files on the source server.

   • For a PostgreSQL database, OMS Community Edition saves logs from the current time for 48 hours by default after the store is started for the first time. If the store fails to start for the first time, you cannot specify a timestamp earlier than the current time for log pulling.

     Note

     • If the store was started for the first time within 48 hours, you can specify any time after the first start time for log pulling.

     • If the store was started for the first time more than 48 hours ago, you can specify any time within the last 48 hours for log pulling.

5. Click Add.