Denis Krivenko

Hi @fisache and @ManuelNeubergerWN! I use `start-thriftserver.sh` to run STS and cannot find a right way to stop it. This is a part of my code how I start and...

Sorry, I think my previous message was not clear enough :) I use Kubernetes too. So I have implemented Deployment similar to yours, but instead of `spark-submit` and long args...

What confuses me is the fact that I cannot find any open source helm chart or other good way to run STS on Kubernetes. Spark Operator is promising but looks...

Yes, there are 7 histograms of executor memory from the beginning to a few minutes before OOMKilled [memory-histograms.zip](https://github.com/delta-io/delta/files/9438522/memory-histograms.zip)

@zsxwing I observe this problem (visible memory leak) on executor pods only. I got the memory histograms above from one specific executor from start to a few minutes before OOMKilled....

I made two heap dumps of the executor memory which is quite close to be OOMKilled. 1. All objects `jmap -dump:format=b,file=executor_10.hprof 14` 2. Live objects `jmap -dump:live,format=b,file=executor_10_live.hprof 14` @zsxwing Would...

Unfortunately I have never used it before, but what `"merge shortest path to GC Root" (exclude weak references)` shows

@zsxwing Yes, of course

No, I didn't set any `spark.cleaner.*` properties before, so the default values are used. I have set `spark.cleaner.referenceTracking.blocking` to `false`, but unfortunately it didn't help. There is the same memory...

@zsxwing The issue is reproducible on Spark 3.3.0 + Delta Lake 2.1.0 Also I read about memory leak in zstd which is used by default for event logs. So I...