EMR StarRocks FE log file fix announcement
In historical versions of the StarRocks service on EMR, the Frontend (FE) component log configuration is invalid. Symlinked log directories accumulate without being cleared automatically, and the disk where FE log files are stored may become full.
Potential impacts
| Item | Details |
|---|---|
| Affected versions | EMR V5.10.X, EMR V3.10.X, and all earlier minor versions |
| Affected component | Frontend (FE) |
| Impact | Symlinked log directories are not cleared automatically. The disk where FE log files are stored may become full. |
Workaround
Redirect the FE log directories (sys_log_dir and audit_log_dir) from symlinked paths to actual disk paths. This lets the log rotation mechanism locate and clear log files correctly.
Step 1: Go to the Configure tab of the StarRocks service
-
Log on to the EMR on ECS console.
-
In the top navigation bar, select the region where your cluster resides and select a resource group based on your business requirements.
-
On the EMR on ECS page, find the cluster and click Services in the Actions column.
-
On the Services tab, find the StarRocks service and click Configure.
Step 2: Add configuration items on the fe.conf tab
-
On the Configure tab, click the fe.conf tab.
-
Click Add Configuration Item.
-
In the dialog box, add the following configuration items and click OK.
Key Value Description sys_log_dir/mnt/disk1/log/starrocksPoints system logs to the actual disk path, bypassing the symlink that prevents automatic log rotation. audit_log_dir/mnt/disk1/log/starrocksPoints audit logs to the actual disk path, bypassing the symlink that prevents automatic log rotation. -
In the dialog box, set Execution Reason and click Save.
Step 3: Restart the Frontend component
-
On the Configure tab, click the Status tab.
-
In the Components section, find the Frontend component and click Restart in the Actions column.
-
In the dialog box, set Execution Reason and click OK.
-
In the confirmation message, click OK.