Hi Chet,
These are the files I have in my lib/ folder with the working log4j2
integration:
-rw-r--r-- 1 robert robert 79966937 Oct 10 13:49 flink-dist_2.10-1.1.3.jar
-rw-r--r-- 1 robert robert90883 Dec 9 20:13
flink-python_2.10-1.1.3.jar
-rw-r--r-- 1 robert robert60547 Dec 9 18:45 lo
I read through the link you provided, Stephan. However, I am still confused. The instructions mention specific jar files for Logback, I am not sure which of the log4j 2.x jars I need to put in the the flink /lib directory. I tried various combinations of log4j-1.2-api-2.8.jar, log4j-slf4j-impl-2.8.
The log just indicates the SignalHandler handles the kill signal and the
process of JobManager exit , and it can not get the reason from it.You may
check the container log from node manager why it was killed.
Best,
Zhijiang--发件人:lini
Hi,
I use yarn manager resource. Recently when disk less 10% , JobManager was
killed. I want to know whether the reason is the disk problem.
log :
2017-02-19 03:20:37,087 INFO
org.apache.flink.yarn.YarnApplicationMasterRunner - RECEIVED
SIGNAL 15: SIGTERM. Shutting down as request
Hi Vinay
Can you provide the LOG file in RocksDB? It helps a lot to figure out the
problems becuse it records the options and the events happened during the
execution. Otherwise configured, it should locate at the path set in
System.getProperty("java.io.tmpdir").
Typically, a large amount of me