qy-liuhuo commented on code in PR #11119:
URL: https://github.com/apache/inlong/pull/11119#discussion_r1774795549
##########
inlong-sdk/dataproxy-sdk/src/main/java/org/apache/inlong/sdk/dataproxy/ConfigConstants.java:
##########
@@ -74,4 +74,6 @@ public class ConfigConstants {
public static String HTTP = "http://";;
public static String HTTPS = "https://";;
+ public static int MAX_MESSAGE_LENGTH = 500 * 1024;
Review Comment:
Now the transmission process of maxMsgSize configuration is as follows:
1. `DataProxy` is configured first
2. `maxMsgSize` is transmitted to the manager along with the `DataProxy`
`heartbeat packet`（in the `extParams` field）
3. The `manager` stores the `extParams` information (containing the
`maxMsgSize` field) in the database
4. `DataProxy` obtains `maxMsgSize` when calling the
`/dataproxy/getIpList/{inlongGroupId}` interface to obtain proxy cluster
information
5. `DataProxy` uses `maxMsgSize` to determine whether the data exceeds the
length limit
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
