-
Notifications
You must be signed in to change notification settings - Fork 88
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
Internal error: 745 shards not a power of 2 #216
Comments
Thanks for the report! I'm not sure exactly why this is happening but some extra information would help. Would you mind building tippecanoe from #220, rerunning your tiling, and sending me the extra log output that you get? On my laptop I get:
but there must be a miscalculation somewhere based on how many CPUs your computer has and how many files it allows open at once. |
Thanks for your reply! Unfortunately, I wasn't able to build it successfully and ran into a couple of errors in the process. However, for context, Tippecanoe is running on a Kubernetes node which means it has access to shared CPU which is quite large. With the way Kubernetes works, I don't think the size of the CPU is also going to be guaranteed a power of 2 which would explain the error. I'll keep trying to build it and comment again if I can get that extra logging. |
Hi, is there any progress on this issue? I've had this problem, but it's not on every machine. Is it caused by environmental issues? |
Same, it was only occurring on certain machines in a Kubernetes cluster so we just ended up using it on the ones that worked. I imagine it has to do with the underlying CPU. |
When trying to convert my GeoJSONs to tiles, I get the error
Internal error: 745 shards not a power of 2
.My tiles end up empty at only 28kb. I'm using Tippecanoe with Ubuntu on Docker. I haven't gotten this issue before but it's suddenly coming up even though nothing has changed with my installation. I'm calling Tippecanoe from Python subprocess using the command below:
Not sure where to go from here and there doesn't seem to be much online about this issue, any tips on debugging?
The text was updated successfully, but these errors were encountered: