This topic describes how to use Alibaba Cloud Simple Log Service to collect the logs of Presto jobs.
Background information
EMR on ACK uses virtual containers to run EMR jobs. After an EMR job is successfully run, the related container is deleted, and resources in the container are released. For clusters for which the auto scaling or timed scheduling feature is enabled, related containers and resources that are used to run EMR jobs are also deleted after the jobs are complete. If the runtime logs of a container are not retained or persisted in a timely manner when a job or service running on EMR on ACK is abnormal, the root cause of the job or service failure is difficult to identify after resources in the container are released. Therefore, we recommend that you enable Simple Log Service to store container logs.
Prerequisites
A Presto cluster is created on the EMR on ACK page of the new EMR console. For more information, see Get started with EMR on ACK.
Simple Log Service is activated. For more information, see Getting Started.
Procedure
Use Simple Log Service to collect container logs. For more information, see Collect text logs from Kubernetes containers in DaemonSet mode.
The following log paths are involved:
If you want to collect standard outputs from containers, you must set the logging path to stdout.
If you want to collect outputs of core dump files from containers, you must set the logging path to /data/trino/hs_err_pid1.log.