Description
When deploying a model using the vllm backend of Triton Server version 25.10, a large number of error logs with the message "Cannot remove future from background; KeyError: <Future at ... state=finished returned NoneType>" are continuously output after sending inference requests to the model. However, the request results are returned normally. Currently, there are no additional exception logs and no effective debugging methods available, making it impossible to locate the root cause and handle the issue.
E1124 02:31:22.019371 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x78543047f020 state=finished returned NoneType>"
E1124 02:31:22.030277 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857a2b699a0 state=finished returned NoneType>"
E1124 02:31:22.038870 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857a2b6be30 state=finished returned NoneType>"
E1124 02:31:22.043864 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857a2b69250 state=finished returned NoneType>"
E1124 02:31:22.076672 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857941dffe0 state=finished returned NoneType>"
E1124 02:31:22.091349 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857941dcbf0 state=finished returned NoneType>"
E1124 02:31:22.097797 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857941dd0a0 state=finished returned NoneType>"
E1124 02:31:22.515902 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x78579419ba10 state=finished returned NoneType>"
E1124 02:31:22.529051 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x78579419bf20 state=finished returned NoneType>"
E1124 02:31:22.550514 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x785430438b60 state=finished returned NoneType>"
E1124 02:31:22.554332 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x785430438ef0 state=finished returned NoneType>"
E1124 02:31:22.639060 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x78543045f020 state=finished returned NoneType>"
E1124 02:31:22.642232 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857941dc770 state=finished returned NoneType>"
E1124 02:31:22.661225 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x78576fa9ffe0 state=finished returned NoneType>"
E1124 02:31:22.675548 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857941de540 state=finished returned NoneType>"
E1124 02:31:22.700992 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857a1363f50 state=finished returned NoneType>"
E1124 02:31:22.712640 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7853e0bcc290 state=finished returned NoneType>"
E1124 02:31:22.718041 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7853e0bcf0b0 state=finished returned NoneType>"
E1124 02:31:22.730276 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857941df710 state=finished returned NoneType>"
E1124 02:31:22.737700 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7853e0bcc800 state=finished returned NoneType>"
E1124 02:31:22.739400 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7853e0bccdd0 state=finished returned NoneType>"
E1124 02:31:22.742066 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7853e0bccbf0 state=finished returned NoneType>"
E1124 02:31:23.252599 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857941dd8e0 state=finished returned NoneType>"
E1124 02:31:23.266090 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857a1f1e450 state=finished returned NoneType>"
E1124 02:31:23.345243 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x78543045c590 state=finished returned NoneType>"
E1124 02:31:23.347122 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857a1360dd0 state=finished returned NoneType>"
E1124 02:31:23.355554 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857a1361fd0 state=finished returned NoneType>"
E1124 02:31:23.363940 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x78576fa9d580 state=finished returned NoneType>"
E1124 02:31:23.368886 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x78576fa9dcd0 state=finished returned NoneType>"
E1124 02:31:23.428142 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857941c27b0 state=finished returned NoneType>"
E1124 02:31:23.843190 568 pb_stub.cc:953] "Cannot remove future from background; KeyError: <Future at 0x7857a1361a30 state=finished returned NoneType>"
Triton Information
Triton version: 25.10
Usage method: Official Triton container (vllm backend)
Are you using the Triton container or did you build it yourself?
I need both the ONNX backend and VLLM backend, so I built a custom Triton image with the following Dockerfile commands:
FROM repo.yxuer.com:30100/nvidia/tritonserver:25.10-py3 AS base
FROM repo.yxuer.com:30100/nvidia/tritonserver:25.10-vllm-python-py3
# Copy ONNX Runtime and TensorRT backends from the base image
COPY --from=base /opt/tritonserver/backends/onnxruntime /opt/tritonserver/backends/onnxruntime
COPY --from=base /opt/tritonserver/backends/tensorrt /opt/tritonserver/backends/tensorrt
Description
When deploying a model using the vllm backend of Triton Server version 25.10, a large number of error logs with the message "Cannot remove future from background; KeyError: <Future at ... state=finished returned NoneType>" are continuously output after sending inference requests to the model. However, the request results are returned normally. Currently, there are no additional exception logs and no effective debugging methods available, making it impossible to locate the root cause and handle the issue.
Triton Information
Triton version: 25.10
Usage method: Official Triton container (vllm backend)
Are you using the Triton container or did you build it yourself?
I need both the ONNX backend and VLLM backend, so I built a custom Triton image with the following Dockerfile commands: