If you call the OpenSearch API or use an OpenSearch SDK to push data, the total number of requests and the total size of data are limited. For more information, see Limits. We recommend that you package the documents to be pushed and push the package.
After the data is uploaded, make sure that you check the return values. If an error code is returned, especially 3007, troubleshoot the error based on the error code and try again. Otherwise, data loss may occur. The data is asynchronously processed. If the system returns OK, this only indicates that the data is received by the system. If an error occurs during data processing, the corresponding error message is displayed in the OpenSearch console. Check the message at the earliest opportunity.
The add command is used to add documents. All fields in a document are updated. If a field in the document is not updated, the field is left empty by default. If the document that corresponds to a primary key ID already exists, the delete operation is performed on the document before the add operation.
The update command is used to update documents. Specific fields in a document are updated. If a field in the document is not updated, the field retains the original value. If a document to be updated already exists, the delete operation is performed before the add operation on the document.
The delete command is used to delete documents. If the document that corresponds to a primary key ID does not exist, the document is deleted.
The total size of data that can be pushed per second by using the HTTP POST method is limited. If the total size of the documents that you upload exceeds 2 MB, the server refuses to receive the parameters and returns an error. For more information, see Limits.
If the error message "connection timed out", "1000 :system error", or "push rate exceeds app quota" is returned when you push data by calling API operations, try again until the push is successful. Note: The error message "push rate exceed app quota" is returned because you push data at a high frequency. However, this error message is more likely to be returned because the documents that are uploaded per second are larger than 2 MB.
If the total number of times that you push data by calling API operations exceeds the upper limit, the error message "request too frequently" is returned. Therefore, we recommend that you package the data to be pushed and push the package. This is more efficient.
We recommend that you perform URL encoding on the URL and body of an HTTP POST request. Otherwise, resolution and signature errors may occur.
When you push incremental data from a data source or by calling API operations, the documents with duplicate primary key values are overwritten.
The rate of synchronizing data from ApsaraDB RDS for MySQL and the size of data that can be synchronized are limited. For more information, see Limits.
A binary log is generated when all the tables in an ApsaraDB RDS for MySQL database are updated. If the number of binary logs that are generated exceeds the upper limit, the data is stacked up and synchronization is delayed. In this case, we recommend that you put the tables that are frequently updated in different databases. Alternatively, we recommend that you enable automatic data synchronization for the primary table in the ApsaraDB RDS for MySQL database and call API operations to synchronize the data in the secondary tables.