dynmap icon indicating copy to clipboard operation
dynmap copied to clipboard

Fix for Breaking S3 Changes

Open kiwikodes opened this issue 1 year ago • 3 comments

Undoing some changes made in #4030 that broke support for S3 (see #4128). These changes will now make sure the appropriate section of the buffer is written to the S3 bucket. Hence resolving #4128.

kiwikodes avatar Jun 30 '24 11:06 kiwikodes

Any update on this?

riipeckx avatar Oct 24 '24 00:10 riipeckx

Unfortunately this is not the end of issues from #4030 for me at least.

The zoom tile generation thread gets stuck in an infinite loop trying to read from s3, and silently failing without any message. This process generates about 2-3MB/s of constant traffic to s3 while not successfully writing zoom tiles.

I wonder if you're having the same issue?

Putting a breakpoint in processZoomFile reveals that the call to S3Client.getObjectAsBytes is failing. image

stewi1014 avatar Oct 24 '24 07:10 stewi1014

@stewi1014 My server have been running for ~6hours for now and still rendering and uploading zoom tiles (not using AWS S3, I'm uploading to Cloudflare R2). As I'm not a Java developer at all I can't ensure I will not be facing an issue soon. Keep us updated :)

riipeckx avatar Oct 24 '24 08:10 riipeckx