[FLINK-5650] Flink-python tests executing cost too long time

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.2.0, 1.3.0
• Fix Version/s: 1.2.1, 1.3.0
• Component/s: API / Python, Tests
• Labels: osx
• Assignee: Chesnay Schepler
• Reporter: shijinkui
• Created: 26/Jan/17 07:43
• Updated: 02/Oct/19 17:48
• Resolved: 17/Mar/17 07:05

Description

When execute `mvn clean test` in flink-python, it will wait more than half hour after the console output below:
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.flink.python.api.PythonPlanBinderTest
log4j:WARN No appenders could be found for logger (org.apache.flink.python.api.PythonPlanBinderTest).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

The stack below:
"main" prio=5 tid=0x00007f8d7780b800 nid=0x1c03 waiting on condition [0x0000700009fd8000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at org.apache.flink.python.api.streaming.plan.PythonPlanStreamer.startPython(PythonPlanStreamer.java:70)
at org.apache.flink.python.api.streaming.plan.PythonPlanStreamer.open(PythonPlanStreamer.java:50)
at org.apache.flink.python.api.PythonPlanBinder.startPython(PythonPlanBinder.java:211)
at org.apache.flink.python.api.PythonPlanBinder.runPlan(PythonPlanBinder.java:141)
at org.apache.flink.python.api.PythonPlanBinder.main(PythonPlanBinder.java:114)
at org.apache.flink.python.api.PythonPlanBinderTest.testProgram(PythonPlanBinderTest.java:83)
at org.apache.flink.test.util.JavaProgramTestBase.testJobWithoutObjectReuse(JavaProgramTestBase.java:174)

this is the jstack:
https://gist.github.com/shijinkui/af47e8bc6c9f748336bf52efd3df94b0

Issue Links

• is duplicated by: FLINK-5331 PythonPlanBinderTest idling extremely long