[FLINK-35040] Revert commons-io to 2.11.0

[1996fanrui]

What is the purpose of the change

The performance of serializerHeavyString regresses since April 3, and had not yet recovered on April 8th.

After running a series of benchmarks, I found FLINK-34955 causes the performance regression.

FLINK-34955 wants to fix CVE issues of common-compress, but it upgrades the commons-io together. I try to revert commons-io to 2.11.0, and the performance is recovered.

Brief change log

• [FLINK-35040] Revert commons-io to 2.11.0
  • Revert part of [FLINK-34955] Upgrade commons-compress to 1.26.0. (#24580)

[flinkbot]

CI report:

• fbdcbb9 Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[slfan1989]

@1996fanrui If we confirm that it's an issue with commons-io, couldn't we resolve it by upgrading commons-io instead? The reason for upgrading commons-io is that common-compress requires a higher version.

[1996fanrui]

Thanks @slfan1989 for the quick review!

@1996fanrui If we confirm that it's an issue with commons-io, couldn't we resolve it by upgrading commons-io instead?

Do you mean upgrading commons-io to the latest version? If yes, I tried upgrading commons-io to 2.16.1, the performance is still not good.

I saw 2.16.1 is the latest version of commons-io[1].

[1] https://mvnrepository.com/artifact/commons-io/commons-io

[slfan1989]

Thanks @slfan1989 for the quick review!

@1996fanrui If we confirm that it's an issue with commons-io, couldn't we resolve it by upgrading commons-io instead?

Do you mean upgrading commons-io to the latest version? If yes, I tried upgrading commons-io to 2.16.1, it doesn't work.

I saw 2.16.1 is the latest version of commons-io[1].

[1] https://mvnrepository.com/artifact/commons-io/commons-io

I'm sorry for any inconvenience caused. The reason for upgrading commons-io is that common-compress requires a higher version. We encounter a "class not found" issue when using commons-io 2.11. If we can't meet the performance requirements, I think we might have to revert FLINK-34955.

[1996fanrui]

It seems reverting it doesn't make sense, I close this PR first.