Mohit Yadav 8f92aa4a8c Remove Virtual Threads : (#27231) ... PostgreSQL JDBC 42.7.7 uses synchronized blocks around network I/O (sending queries, reading responses). With virtual threads, a thread that blocks inside synchronized gets pinned to its carrier thread — it cannot unmount even when waiting for I/O. With -XX:ActiveProcessorCount=2, there are exactly 2 ForkJoinPool carrier threads. The moment 2 concurrent SQL queries are executing on virtual threads, both carrier threads are pinned. The health probe's virtual thread becomes runnable but can't be scheduled — no carrier thread is free. Probe times out. Repeat indefinitely. Disabling virtual threads switches Jetty back to a 150-thread platform thread pool. Even if 100 threads are blocked waiting for DB connections, 50 remain available for the health probe and other requests. The complete deadlock is impossible with platform threads		2026-04-12 22:30:28 -07:00
..
distributed-test	Reindex Work - Perf , Metrics , Benchmarking and More (#26231)	2026-03-10 08:10:46 +05:30
debug-latency.sh	Revamp metrics, Add Request Latencies, breakdown database, search latencies (#22259)	2025-07-10 11:34:30 -07:00
openmetadata-server-start.sh	Remove Virtual Threads : (#27231)	2026-04-12 22:30:28 -07:00
openmetadata.sh	Remove Virtual Threads : (#27231)	2026-04-12 22:30:28 -07:00
thread-monitor.sh	Reindex Work - Perf , Metrics , Benchmarking and More (#26231)	2026-03-10 08:10:46 +05:30