Skip to content

Troubleshooting / Func Execution Unresponsive

Func execution unresponsive may have multiple possibilities, and it needs to be distinguished according to different situations.

Specific manifestations are:

  1. When the browser accesses the interface, it stays in the loading state for a long time.
  2. When calling the interface via curl, there is no response for a long time.

At this time, it is necessary to write a test function in DataFlux Func and configure it as a "Sync API (old version: Auth Link)" to help determine the cause.

The test function is as follows:

Python
1
2
3
@DFF.API('Test Func')
def test_func():
    return 'OK'

1. Test Function Normal

Possible causes and solutions:

Possible Cause Solution
The called function indeed requires a long time to run Contact the function developer to troubleshoot the issue

2. Unable to Publish Test Function, or Calling Test Function Unresponsive

Possible causes and solutions:

Possible Cause Solution
Queue Blocking Go to "About / Get System Report / Clear Work Queue"
Redis Connection Issue Check if the Redis connection configuration is correct and restart the entire DataFlux Func

About "Redis Connection Issue"

In the scenario where DataFlux Func is deployed in k8s, if the k8s cluster crashes and restarts or the Redis Pod crashes and restarts, but DataFlux Func itself does not restart, it may cause all function calls to be unresponsive.

This may be because after the k8s cluster or Redis Pod restarts, the old connection between DataFlux Func and Redis is not closed, or DataFlux Func cannot be aware that the Redis connection has been disconnected, causing the DataFlux Func task process to always wait for messages from Redis but never communicate normally.

At this time, while ensuring that Redis is running normally, restarting the entire DataFlux Func can solve this problem.