Ah, I see. I am guessing most of the CPU cycles are burned by the table
service.
You can try to disable that feature as it is still under developer preview
mode. You can run standalone as `bin/pulsar standalone --no-stream-storage`.
- Sijie
On Sun, Jan 31, 2021 at 10:52 PM Wesley Peng wrote:
Can you help check with log output?
$ tail -f pulsar-standalone-PresentSpicy-VM.log
14:45:14.281 [main-EventThread] INFO
org.apache.distributedlog.logsegment.PerStreamLogSegmentCache -
Hi Wesley,
The CPU usage might be coming from some background tasks. Do you happen to
have the log of the standalone server? This might give some insights to the
problem.
- Sijie
On Sun, Jan 31, 2021 at 9:58 PM Wesley Peng wrote:
> I deployed a standalone pulsar server on a two cores VPS,
I deployed a standalone pulsar server on a two cores VPS, which was new
installed.
Even there is not any jobs running on pulsar, it still consumes CPU about 15+%.
'top' shows the java process takes it.
Can you help explain this? Thank you.
Regards.
