[fix][proxy] Fix proxy OOM by replacing TopicName with a simple conversion method

[BewareMyPower]

Fixes #24445

Motivation

See #24458 for details. However

• The solution of [fix][proxy]Pulsar Proxy OOMs because it forgets to clear the topic name cache #24458 introduces new configurations and an extra scheduled task.
• [fix] Fix memory leak in TopicName cache and reduce heap memory usage through deduplication #24457 is an alternative solution that aims at providing a better designed cache that can shrink automatically. It might be able to fix this issue as well, but the impact might be wide and needs more careful review and discussion.

After reviewing the usages of TopicName in pulsar-proxy module, I found the only case is to convert a user-provided topic to the full topic name. Using TopicName has many unnecessary overhead like parsing a NamespaceName (see the cost from the benchmark here), or maintaining the TopicName object in a global cache that requires a thread-safe access via ConcurrentHashMap.

Modifications

Introduce a new method TopicName#toFullTopicName for the purpose of TopicName in pulsar-proxy module. Instead of using a global cache, just call this method directly for the conversion.

It does not introduce any new configuration. From the benchmark, it's only 2.2x slower than the TopicName#get, when there are only 200k keys. But it's faster than TopicName#get.

However, it saves memory and the performance should be acceptable that it can be executed 8.5 millions in 1 second.

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: BewareMyPower#46

[nodece]

LGTM, I think we can move toFullTopicName to the TopicName class.

[BewareMyPower]

I think we can move toFullTopicName to the TopicName class.

Yes. But let's keep it in TopicNameUtils for now in case there are some conflicts.

[BewareMyPower]

I changed my idea and moved the method to TopicName because it has a duplicated method with #24463

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 80.76923% with 10 lines in your changes missing coverage. Please review.

Project coverage is 74.28%. Comparing base (bbc6224) to head (83d9e82).
Report is 1181 commits behind head on master.

Files with missing lines	Patch %	Lines
...ava/org/apache/pulsar/common/naming/TopicName.java	80.48%	4 Missing and 4 partials ⚠️
...rg/apache/pulsar/common/api/raw/MessageParser.java	66.66%	1 Missing ⚠️
...apache/pulsar/proxy/server/LookupProxyHandler.java	66.66%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #24465      +/-   ##
============================================
+ Coverage     73.57%   74.28%   +0.71%     
- Complexity    32624    32765     +141     
============================================
  Files          1877     1868       -9     
  Lines        139502   145547    +6045     
  Branches      15299    16657    +1358     
============================================
+ Hits         102638   108126    +5488     
+ Misses        28908    28863      -45     
- Partials       7956     8558     +602     

Flag	Coverage Δ
inttests	26.87% <26.92%> (+2.28%)	⬆️
systests	23.35% <26.92%> (-0.98%)	⬇️
unittests	73.77% <80.76%> (+0.93%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...apache/pulsar/proxy/server/ParserProxyHandler.java	91.95% <100.00%> (+0.09%)	⬆️
...rg/apache/pulsar/common/api/raw/MessageParser.java	52.94% <66.66%> (+1.42%)	⬆️
...apache/pulsar/proxy/server/LookupProxyHandler.java	60.41% <66.66%> (-0.18%)	⬇️
...ava/org/apache/pulsar/common/naming/TopicName.java	91.90% <80.48%> (-4.16%)	⬇️

... and 1085 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.