Environment
- Deployment: Kubernetes
- Runtime Version:
0.0.7-local
Problem Description
We are encountering an issue where OpenAI blocks become unresponsive when a workflow involving the Speech-to-Text (STT) block is executed. Additionally, the workflow containing the STT block itself hangs indefinitely and does not return any results.
Observations
- When the
STT workflow is running, all concurrent or subsequent OpenAI block executions appear to be blocked.
- Pod metrics indicate that the relevant process within the
dify-plugin-daemon pod consumes 1 full CPU core during this state.
- This behavior leads us to suspect that the daemon might be single-threaded or facing a bottleneck related to concurrent processing, particularly when handling
STT operations.
Questions
- Is there a known issue or potential reason why the Speech-to-Text (
STT) block would cause other OpenAI blocks to hang and fail to complete itself?
- What are the recommended practices or configurations for deploying and managing the
dify-plugin-daemon on Kubernetes, potentially including considerations for scaling or concurrency to handle workloads like STT?
Thank you for your support.
Environment
0.0.7-localProblem Description
We are encountering an issue where
OpenAIblocks become unresponsive when a workflow involving the Speech-to-Text (STT) block is executed. Additionally, the workflow containing theSTTblock itself hangs indefinitely and does not return any results.Observations
STTworkflow is running, all concurrent or subsequentOpenAIblock executions appear to be blocked.dify-plugin-daemonpod consumes 1 full CPU core during this state.STToperations.Questions
STT) block would cause otherOpenAIblocks to hang and fail to complete itself?dify-plugin-daemonon Kubernetes, potentially including considerations for scaling or concurrency to handle workloads likeSTT?Thank you for your support.