Sergei Ustimenko

> Tests with failures: > - org.opensearch.action.admin.indices.create.CreateIndexIT.testCreateAndDeleteIndexConcurrently > - org.opensearch.action.admin.indices.create.CreateIndexIT.classMethod > > 5600 tests completed, 2 failed, 407 skipped Looks like a failure due to a flaky test, more here:...

Hi folks, this PR is ready for review, could someone please take a look? Thanks a lot!

>Side question: Do we also eventually plan for support for REST_EXCEPTION_SKIP_STACK_TRACE as well? @karenyrx, good question. What would be use cases here and what an implementation might look like?

Here are a few examples to better show the outcome of this change. **Http Bulk endpoint (both `error_trace=true` and `false` produce the same outcome):** Http Bulk ``` { "took": 2,...

@karenyrx >Is this a bug in HTTP bulk (should error_trace=true not pritn out the stack trace)? Or is this intentional and the gRPC side also be following the same mechanism...

@karenyrx **After the latest changes here's how the Grpc errors look like:** Search Endpoint `error_trace=false` ``` Response trailers received: content-type: application/grpc Sent 1 request and received 0 responses ERROR: Code:...

@karenyrx could you please have a quick look? All the points seem to be covered and as for the Http Bullk API handling of `error_trace`, I've raised a separate issue...

Seems like a flaky test failure ``` > Task :server:internalClusterTest Tests with failures: - org.opensearch.indices.replication.WarmIndexSegmentReplicationIT.testNodeDropWithOngoingReplication 5584 tests completed, 1 failed, 63 skipped > Task :server:internalClusterTest FAILED ```

@reta would you be able to take a look whenever time permits? This change is a tiny bit of polishing of netty-related testing code. Hope it makes it easier to...

Seems like a failure in spotless in unrelated module, I guess rerunning CI should do the trick ``` FAILURE: Build failed with an exception. * What went wrong: Execution failed...