jina: Flow/Deployment would raise timeout warning even if containerized executor is running

Describe your problem


I follow the tutorial here and create my own docker image called “my_exec” for an executor. It works perfectly when I use jina executor --uses docker://my_exec to serve the executor and use a Client object to use it. However, serving by using a Flow or a Deployment object would always raise a timeout warning and hang indefinitely as shown in the following screenshots.

My executor needs to load a large neural net to initialize, which takes about 1 minute. I thought this loading time could be the cause of the problem and tried setting timeout-ready to -1, but I still cannot get rid of this warning.

Another possible cause maybe that the entrypoint of my docker image is ENTRYPOINT ["conda", "run", "-n", "legacy_subtitle_punc", "jina", "executor", "--uses", "config.yml"] where I activate a conda environment before calling jina instead of calling jina directly. Does this have something to do with the problem? If it is the cause, are there any workarounds that still allow me to use conda?

Environment

  • jina 3.14.1
  • docarray 0.21.0
  • jcloud 0.2.6
  • jina-hubble-sdk 0.35.0
  • jina-proto 0.1.13
  • protobuf 3.20.3
  • proto-backend cpp
  • grpcio 1.47.5
  • pyyaml 5.3.1
  • python 3.7.16
  • platform Linux
  • platform-release 3.10.0-957.el7.x86_64
  • platform-version #1 SMP Thu Nov 8 23:39:32 UTC 2018
  • architecture x86_64
  • processor x86_64
  • uid 274973452769639
  • session-id d8df0eec-da9b-11ed-9f15-fa163ef99967
  • uptime 2023-04-14T16:10:40.727171
  • ci-vendor (unset)
  • internal False
  • JINA_DEFAULT_HOST (unset)
  • JINA_DEFAULT_TIMEOUT_CTRL (unset)
  • JINA_DEPLOYMENT_NAME (unset)
  • JINA_DISABLE_UVLOOP (unset)
  • JINA_EARLY_STOP (unset)
  • JINA_FULL_CLI (unset)
  • JINA_GATEWAY_IMAGE (unset)
  • JINA_GRPC_RECV_BYTES (unset)
  • JINA_GRPC_SEND_BYTES (unset)
  • JINA_HUB_NO_IMAGE_REBUILD (unset)
  • JINA_LOG_CONFIG (unset)
  • JINA_LOG_LEVEL (unset)
  • JINA_LOG_NO_COLOR (unset)
  • JINA_MP_START_METHOD (unset)
  • JINA_OPTOUT_TELEMETRY (unset)
  • JINA_RANDOM_PORT_MAX (unset)
  • JINA_RANDOM_PORT_MIN (unset)
  • JINA_LOCKS_ROOT (unset)
  • JINA_K8S_ACCESS_MODES (unset)
  • JINA_K8S_STORAGE_CLASS_NAME (unset)
  • JINA_K8S_STORAGE_CAPACITY (unset)
  • JINA_STREAMER_ARGS (unset)

Screenshots

when using Flow to serve the executor (Deployment raises the same warning except that there are no other logs printed): 爱奇艺20230414155409

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 28 (16 by maintainers)

Most upvoted comments

Can you run this?

docker run -it --entrypoint "conda" my_exec run -n legacy_subtitle_punc jina -v

I want to understand what Jina version is running inside there.

I got 3.14.1 after running it