-
Notifications
You must be signed in to change notification settings - Fork 8
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
Write end dead child number [34542970] in file [Comments.xml] whilst parsing archive #10
Comments
What could be possibly wrong? |
I got a very similar error. Seems to be the same as the first error mentioned in issue #8 . Potentially moving the stackoverflow data to a new hard drive is a fix that might work? Here's my log: 19:55:47.696 [pool-2-thread-1] DEBUG org.tools4j.stacked.index.XmlFileParser - 61000000 comments rows read from xml... |
I too experience this issue. I've tried it a few times and it always crashes at a different child number, so I suppose (as did the previous posters) that it doesn't have something to do with the input data itself (like a malformed string or something like that). I did monitor CPU, RAM and disk space usage, all were within normal parameters for the entire run... Update: My mitigation for now is to host an instance of Kiwix-Serve, which is an entirely different application but can also serve an offline dump of Stack Overflow answers (among other sources). Maybe this can help some future visitors with the same problem, too :) |
I've downloaded these files
When I try to index them I get this error:
The text was updated successfully, but these errors were encountered: