panbingkun

Just for verification, let it run GA first.

Just as a record - log4j2 version 2.22.1 https://github.com/apache/logging-log4j2/blob/rel/2.22.1/log4j-api/src/main/java/org/apache/logging/log4j/spi/AbstractLogger.java#L252-L254 https://github.com/apache/logging-log4j2/blob/rel/2.22.1/log4j-api/src/main/java/org/apache/logging/log4j/spi/AbstractLogger.java#L2336-L2346 https://github.com/apache/logging-log4j2/blob/8469975a4f2b1f8f1bd4f25ca6d1989a52aefc1b/log4j-api/src/main/java/org/apache/logging/log4j/status/StatusLogger.java#L480-L487 https://github.com/apache/logging-log4j2/blob/rel/2.22.1/log4j-api/src/main/java/org/apache/logging/log4j/status/StatusLogger.java#L82-L83 - log4j2 version 2.23.0 https://github.com/apache/logging-log4j2/blob/rel/2.23.0/log4j-api/src/main/java/org/apache/logging/log4j/status/StatusLogger.java#L747-L752 - The related commit that caused this change is:

@LuciferYang @dongjoon-hyun The version `2.23.1` of log4j2 has been released, which has resolved the issue with the `StatusLogger` in the version `2.23.0`, as follows: Let it run through GA first.

> It seems that one of `ClientStreamingQuerySuite` test hangs due to the independent flakiness. Could you re-trigger it when it fails? Sure, let me continue to observe and verify.

@dongjoon-hyun To be more `reliable`, I will convert this pr from `draft` to `review` until GA can run successfully. I have tried the test `ClientStreamingQuerySuite ` several times, but unfortunately,...

> @panbingkun We can enable the debug logs of the RemoteSparkSession subclass to facilitate troubleshooting. Done.

GA runs successfully, as recorded below: https://github.com/panbingkun/spark/runs/22547066941 Let me verify it for several times.

There are still some problems. After I finish this PR https://github.com/apache/spark/pull/45551, I will carefully analyze it.

> Please let us know if there is any change on this PR. In the previous tests, I found a case `hang`. I'll rebase it again

After it: