[CELEBORN-1368] Log celeborn config for debugging purposes

[akpatnam25]

What changes were proposed in this pull request?

Log celeborn config for debugging purposes.

Why are the changes needed?

Help with debugging

Does this PR introduce any user-facing change?

No

How was this patch tested?

tested the patch internally.

[akpatnam25]

cc @waitinfuture @SteNicholas @FMX can you guys please take a look? thanks.

[SteNicholas]

@akpatnam25, why does this need to log celeborn config? Could user use /conf REST API to get the config? BTW, if this need to log celeborn log, you could invoke HttpService#getConf method to log.

[akpatnam25]

@akpatnam25, why does this need to log celeborn config? Could user use /conf REST API to get the config? BTW, if this need to log celeborn log, you could invoke HttpService#getConf method to log.

We do not have the REST api changes internally yet, as we are running with 0.4 still. This would unblock us quick, in the long term I agree we should use the /conf REST API. I will use the HttpService#getConf, I did not know it existed.

[waitinfuture]

Hi @akpatnam25 , please run UPDATE=1 build/mvn clean test -pl common -am -Pspark-3.3 -Dtest=none -DwildcardSuites=org.apache.celeborn.ConfigurationSuite to update the doc since configs changed in this PR.

[FMX]

I think this PR can be changed.

[akpatnam25]

@SteNicholas @pan3793 @FMX @waitinfuture I have updated this PR. please take another look, thanks

[FMX]

@akpatnam25 There is a compilation error that needs to be fixed first.

[akpatnam25]

@akpatnam25 There is a compilation error that needs to be fixed first.

I accidentally deleted a line! Should be fixed now. @FMX

[FMX]

LGTM. Thanks. Merged into main(v0.5.0).

[akpatnam25]

thanks for the reviews @SteNicholas @FMX @pan3793 @waitinfuture !!