flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sunjincheng (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-14479) Strange exceptions found in log file after executing `test_udf.py`
Date Mon, 09 Dec 2019 02:07:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-14479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991059#comment-16991059
] 

sunjincheng commented on FLINK-14479:
-------------------------------------

I have reset the fix version to 1.11, but always can fix it before the 1.10 release.

> Strange exceptions found in log file after executing `test_udf.py`
> ------------------------------------------------------------------
>
>                 Key: FLINK-14479
>                 URL: https://issues.apache.org/jira/browse/FLINK-14479
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / Python
>            Reporter: sunjincheng
>            Assignee: Wei Zhong
>            Priority: Major
>             Fix For: 1.11.0
>
>         Attachments: screenshot-1.png
>
>
> There are several strange exceptions as follow in `${flink_source}/build-target/log/flink-${username}-python-udf-boot-${machine_name}.local.log`
after executing `${flink_source}/flink-python/pyflink/table/tests/test_udf.py`:
> Traceback (most recent call last):
> {code:java}
>  File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/runpy.py",
line 193, in _run_module_as_main
>  "__main__", mod_spec)
>  File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/runpy.py",
line 85, in _run_code
>  exec(code, run_globals)
>  File "/Users/zhongwei/flink/flink-python/pyflink/fn_execution/sdk_worker_main.py", line
30, in <module>
>  apache_beam.runners.worker.sdk_worker_main.main(sys.argv)
>  File "/Users/zhongwei/pyflink_env/py37/lib/python3.7/site-packages/apache_beam/runners/worker/sdk_worker_main.py",
line 148, in main
>  sdk_pipeline_options.view_as(pipeline_options.ProfilingOptions))
>  File "/Users/zhongwei/pyflink_env/py37/lib/python3.7/site-packages/apache_beam/runners/worker/sdk_worker.py",
line 133, in run
>  for work_request in control_stub.Control(get_responses()):
>  File "/Users/zhongwei/pyflink_env/py37/lib/python3.7/site-packages/grpc/_channel.py",
line 364, in __next__
>  return self._next()
>  File "/Users/zhongwei/pyflink_env/py37/lib/python3.7/site-packages/grpc/_channel.py",
line 347, in _next
>  raise self
> grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with:
>  status = StatusCode.CANCELLED
>  details = "Runner closed connection"
>  debug_error_string = "{"created":"@1571660342.057172000","description":"Error received
from peer ipv6:[::1]:52699","file":"src/core/lib/surface/call.cc","file_line":1052,"grpc_message":"Runner
closed connection","grpc_status":1}"{code}
> It appears randomly when executing test cases of blink planner. Although it does not
affect test results we need to find out why it appears.
> Welcome any feedback!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message