Milvus unavailability may lead to thread unavailability in the system.

[saber-wang]

Bug Description

Milvus unavailability may lead to thread unavailability in the system.

Reproduction

1. Add the Milvus component with an incorrect URL (e.g., the default value).
2. Run the tenant.
3. You can observe that requests never complete.

Expected behavior

Properly complete the request and return an error response.

Who can help?

@italojohnny

It has been confirmed that the issue is caused by this section of code, and it can be mitigated by setting LAGFLOW_PRETTY_LOGS=false.

langflow/src/backend/base/langflow/logging/logger.py

Lines 236 to 246 in eed7dee

	log_stdout_pretty = os.getenv("LAGFLOW_PRETTY_LOGS", "true").lower() == "true"
	if log_stdout_pretty:
	logger.configure(
	handlers=[
	{
	"sink": RichHandler(rich_tracebacks=True, markup=True),
	"format": log_format,
	"level": log_level.upper(),
	}
	]
	)

Operating System

mac os 15

Langflow Version

1.3.3

Python Version

3.12

Screenshot

No response

Flow File

No response

[dosubot]

The issue of thread unavailability when Milvus is unreachable can be mitigated by setting the LAGFLOW_PRETTY_LOGS environment variable to false. This setting affects the logging configuration, where enabling pretty logs (true) can lead to performance issues, especially in high-load scenarios or when external dependencies like Milvus are not available. By setting LAGFLOW_PRETTY_LOGS=false, the system uses a more performance-oriented logging format, which helps prevent requests from hanging indefinitely when Milvus is unreachable. This adjustment is particularly useful in production environments to ensure smoother operation and better resource management.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}