[Bug] Reduce excessive repeated log when memory quota is not set

[tenfyzhong]

Description

The following log message is emitted too frequently:

available memory quota is not set, skip scan

In one observed case, this single message produced nearly 2,000,000 lines.

Impact

• Significant log volume and storage overhead
• Important logs are drowned out by repeated noise
• Potential extra I/O overhead from excessive logging

Expected Behavior

When memory quota is not set, this message should be rate-limited, deduplicated, or logged once per component/time window.

Actual Behavior

The same message is repeatedly printed at very high frequency (about 2 million lines in one case).

Suggested Fix

• Add rate limiting or sampling for this log
• Or log this condition once and suppress repetitive duplicates
• Optionally emit periodic summary counters instead of per-event logging