Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heap Summary Connection Issues #389

Open
KhrysAK47 opened this issue Feb 25, 2024 · 4 comments
Open

Heap Summary Connection Issues #389

KhrysAK47 opened this issue Feb 25, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@KhrysAK47
Copy link

Description

We have a server running and were experiencing some issues so decided to use spark, which is why we setup the server to automatically run /spark heapsummary every 30 minutes to check how it performs overtime and compare results that way, however, we noticed that after adding this, for some reason all players started to have 1000 ping and getting kicked for timeout. This was never an issue for us and it is not the hosting provider we use as it only started happening after enabling that, and it fixes itself when removing that.

Reproduction Steps

  • Install spark
  • Make it execute /spark heapsummary every 15-30 minutes
  • Wait

Expected Behaviour

It should not affect player connectivity at all

Platform Information

  • Minecraft Version: 1.20.4
  • Platform Type: Server under a proxy
  • Platform Brand: Paper
  • Platform Version: 9e171ef

Spark Version

v1.10.34

Logs and Configs

No response

Extra Details

No response

@KhrysAK47 KhrysAK47 added the bug Something isn't working label Feb 25, 2024
@KhrysAK47
Copy link
Author

(It is not always at 1000ms, it happens every 1-2 hours in our case with it running).

@SirYwell
Copy link

SirYwell commented Mar 3, 2024

That command will typically trigger a GC run, and the duration of collecting the required data also depends on the (live) heap size. It shouldn't cause people to time out.

What Java version are you using exactly?

@KhrysAK47
Copy link
Author

Java 17

@SirYwell
Copy link

SirYwell commented Mar 3, 2024

You could try profiling all threads (/spark profiler start --thread *) during the execution of the command (start shortly before, stop shortly after). Maybe that provides any useful information what's going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants