Thanks for your kind reply. But I still have some question. What does the logging level mean in your system? Why do you need to re-deploy the cluster to change the logging level? As far as I know, the debugging information can be divided into level like info, warn, error, etc. Is these information totally logged during the system running? And then they can further be analyzed by category them by level?
Best, Stephen > On Apr 19, 2018, at 7:19 AM, Kien Truong <duckientru...@gmail.com> wrote: > > Hi, > > Our most useful tool when debugging Flink is actually the simple log files, > because debugger just slow things down too much for us. > > However, having to re-deploy the entire cluster to change the logging level > is a pain (we use YARN), > > so we would really like an easier method to change the logging level at > runtime. > > > Regards, > > Kien > > > On 4/19/2018 5:53 AM, Qian Ye wrote: >> Hi >> >> I’m wondering if new debugging methods/tools are urgent for Flink >> development. I know there already exists some debug methods for Flink, e.g., >> remote debugging of flink >> clusters(https://cwiki.apache.org/confluence/display/FLINK/Remote+Debugging+of+Flink+Clusters). >> But are they are convenient enough? >> >> Best regards.
