Stack traces as standard error in job logs

bidek56 — Fri, 31 Oct 2025 12:50:57 GMT

When using DBR 16.4, I am seeing a lot of Stack traces as standard error in jobs, any idea why they are showing up and how to turn then off? Thx

"FlagSettingCacheMetricsTimer" id=18 state=WAITING
- waiting on <0x2d1573c6> (a java.util.TaskQueue)
- locked <0x2d1573c6> (a java.util.TaskQueue)
at java.base@17.0.16/java.lang.Object.wait(Native Method)
at java.base@17.0.16/java.lang.Object.wait(Object.java:338)
at java.base@17.0.16/java.util.TimerThread.mainLoop(Timer.java:537)
at java.base@17.0.16/java.util.TimerThread.run(Timer.java:516)

"LDBasedSafeFlagClient" id=17 state=WAITING
- waiting on <0x169e4ba4> (a java.util.TaskQueue)
- locked <0x169e4ba4> (a java.util.TaskQueue)
at java.base@17.0.16/java.lang.Object.wait(Native Method)
at java.base@17.0.16/java.lang.Object.wait(Object.java:338)
at java.base@17.0.16/java.util.TimerThread.mainLoop(Timer.java:537)
at java.base@17.0.16/java.util.TimerThread.run(Timer.java:516)

"process reaper (pid 2011)" id=15 state=RUNNABLE (running in native)
at java.base@17.0.16/java.lang.ProcessHandleImpl.waitForProcessExit0(Native Method)
at java.base@17.0.16/java.lang.ProcessHandleImpl$1.run(ProcessHandleImpl.java:150)
at java.base@17.0.16/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base@17.0.16/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base@17.0.16/java.lang.Thread.run(Thread.java:840)

Locked synchronizers: count = 1
- java.util.concurrent.ThreadPoolExecutor$Worker@5d7d8613

"Notification Thread" id=12 state=RUNNABLE

"Common-Cleaner" id=11 state=TIMED_WAITING
- waiting on <0x6df3bc1d> (a java.lang.ref.ReferenceQueue$Lock)
- locked <0x6df3bc1d> (a java.lang.ref.ReferenceQueue$Lock)
at java.base@17.0.16/java.lang.Object.wait(Native Method)
at java.base@17.0.16/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:155)
at java.base@17.0.16/jdk.internal.ref.CleanerImpl.run(CleanerImpl.java:140)
at java.base@17.0.16/java.lang.Thread.run(Thread.java:840)
at java.base@17.0.16/jdk.internal.misc.InnocuousThread.run(InnocuousThread.java:162)

"Signal Dispatcher" id=4 state=RUNNABLE

"Finalizer" id=3 state=WAITING
- waiting on <0x470d84e1> (a java.lang.ref.ReferenceQueue$Lock)
- locked <0x470d84e1> (a java.lang.ref.ReferenceQueue$Lock)
at java.base@17.0.16/java.lang.Object.wait(Native Method)
at java.base@17.0.16/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:155)
at java.base@17.0.16/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:176)
at java.base@17.0.16/java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:172)

"Reference Handler" id=2 state=RUNNABLE
at java.base@17.0.16/java.lang.ref.Reference.waitForReferencePendingList(Native Method)
at java.base@17.0.16/java.lang.ref.Reference.processPendingReferences(Reference.java:253)
at java.base@17.0.16/java.lang.ref.Reference$ReferenceHandler.run(Reference.java:215)

Re: Stack traces as standard error in job logs

bidek56 — Fri, 31 Oct 2025 17:02:30 GMT

spark.databricks.driver.disableJvmThreadDump=true

This setting will remove the ST.

topic Stack traces as standard error in job logs in Data Engineering

Stack traces as standard error in job logs

Re: Stack traces as standard error in job logs