SQL

Access the flink_jm_8c32g container and start the JobManager and TaskManager in cluster mode. Run the source /etc/profile command each time you access the container again.
```
docker exec -it flink_jm_8c32g /bin/bash
source /etc/profile
cd /usr/local/flink-1.16.3/bin
./start-cluster.sh
```
Check whether the JobManager and TaskManager are started.
1. Check the flink_jm_8c32g container for the StandaloneSessionClusterEntrypoint process.
```
source /etc/profile
jps
```
2. Check the flink_tm1_8c32g and flink_tm2_8c32g containers for the TaskManagerRunner process. The following uses flink_tm1_8c32g as an example.
```
docker exec -it flink_tm1_8c32g /bin/bash
source /etc/profile
jps
```

Start Nexmark in the flink_jm_8c32g container.

docker exec -it flink_jm_8c32g /bin/bash
source /etc/profile
cd /usr/local/nexmark/bin
./setup_cluster.sh

Access the flink_tm1_8c32g and flink_tm2_8c32g containers and check whether Nexmark is started. If the CpuMetricSender process is found, Nexmark is started.
```
docker exec -it flink_tm1_8c32g /bin/bash
source /etc/profile
jps
exit
```

Execute the Nexmark test case Query0 in the flink_jm_8c32g container.

       
            docker exec -it flink_jm_8c32g /bin/bash
source /etc/profile
cd /usr/local/nexmark/bin
sh run_query.sh q0
exit

Figure 1 Query0 execution result

Check the latest .out log of Flink in the TaskManager container. If the log content contains "Loading Task Native Execution Library", the native SO library has been properly loaded. If the log content contains "welcome to native", the OmniStream Flink Native feature has been enabled.

       
            docker exec -it flink_tm1_8c32g /bin/bash 
cd /usr/local/flink-1.16.3/log

Figure 2 Log output

Parent topic: Using the Feature