Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-5331

PythonPlanBinderTest idling extremely long

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 1.2.0
    • Fix Version/s: 1.2.1, 1.3.0
    • Component/s: Python API, Tests
    • Labels:
      None

      Description

      When running mvn clean verify locally, the PythonPlanBinderTest takes sometimes extremely long to finish. The latest build took more than 900 seconds to complete.

      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.
      Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 923.586 sec - in org.apache.flink.python.api.PythonPlanBinderTest
      
      Results :
      
      Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
      

      Additionally I see a lot of python processes (~ 70-80) on my system doing effectively nothing. This behaviour seems really strange to me. I think it would be great to revisit this test case to see whether we can streamline it a little bit better.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                till.rohrmann Till Rohrmann
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: