New RunLLM response generated: >>>*# Question* Hi all, I'm having issues with map_task. Trying to run the most basic example but no containers start for two hours and after that I get an error:

RuntimeExecutionError: max number of system retry attempts [51/50] exhausted. Last known status message: Handler not registered for NodeKind [array]

I just updated flyte-core (it's installed with the helm chart) and flytekit, both to 1.13.0 but that didn't change anything. Would anyone be able to point out to what might be the issue? # Answer The error you're encountering,

Handler not registered for NodeKind [array]

, suggests that the FlytePropeller is not correctly handling the

ArrayNode

type. This can happen if the necessary plugins or configurations for handling array tasks are not properly set up. 1. Check FlytePropeller Configuration: Ensure that the FlytePropeller is configured to handle array tasks. This involves verifying that the necessary plugins are enabled and correctly configured in the FlytePropeller configuration file. 2. Verify Plugin Installation: Make sure that the Flyte array plugin is installed and properly integrated. This plugin is essential for handling array tasks. 3. Check for Multiple Propellers: Ensure that there are no multiple instances of FlytePropeller running, as this can cause conflicts and lead to the error you're seeing. 4. Enable Finalizers: If not already done, enable finalizers in your Flyte deployment to prevent premature deletion of resources. Would you like more detailed steps on how to check and configure these settings? Sources: - Flyte discussion on finalizers - Flyte discussion on unexpected pod deletions - Flyte issue on array plugin Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1721132155.023299 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.