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.

Sign up for GitHub

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

Jump to bottom

Workers #33

Open
claytondukes opened this issue Jun 22, 2020 · 1 comment
Open

Workers #33

claytondukes opened this issue Jun 22, 2020 · 1 comment

Comments

@claytondukes
Copy link

claytondukes commented Jun 22, 2020 •
edited
Loading

I'm curious about the -w option. I have a 40GB file to import but it doesn't seem to matter how much CPU or mem I give the system. I have 192 cores and ~300GB ram but can't get -w to go past -w 7. I have 6 nodes in this cluster.

2020/06/22 16:20:36 error during bulk operation, check error details; maybe try fewer workers (-w) or increase thread_pool.bulk.queue_size in your nodes

FWIW, htop shows barely any utilization while I am running the import.
Am I doing something wrong?
@miku
Copy link
Owner

miku commented Jun 22, 2020

Thanks for the bug report! I'll prioritize the improved error reporting, which I meant to implement for some time now.

Apart from that, I do not see any error (and usage should be more or less self-explanatory).

javfg added a commit to opentargets/platform-output-support that referenced this issue Sep 18, 2024
@javfg
Fix esbulk errors
ce1db3c 
esbulk seems to have been causing errors with the previous settings.
We did not see them before because they do not halt the image building
process, but the db becomes inconsistent, as documents fail to import.

According to issues in the library github:

miku/esbulk#33

and the readme:

https://github.com/miku/esbulk?tab=readme-ov-file#esbulk

Using default settings might solve those errors. So far, it seems to
be working.
jdhayhurst pushed a commit to opentargets/platform-output-support that referenced this issue Sep 25, 2024
@javfg @jdhayhurst
Fix esbulk errors
6103d1d 
esbulk seems to have been causing errors with the previous settings.
We did not see them before because they do not halt the image building
process, but the db becomes inconsistent, as documents fail to import.

According to issues in the library github:

miku/esbulk#33

and the readme:

https://github.com/miku/esbulk?tab=readme-ov-file#esbulk

Using default settings might solve those errors. So far, it seems to
be working.
jdhayhurst pushed a commit to opentargets/platform-output-support that referenced this issue Sep 25, 2024
@javfg @jdhayhurst
Fix esbulk errors
a12b778 
esbulk seems to have been causing errors with the previous settings.
We did not see them before because they do not halt the image building
process, but the db becomes inconsistent, as documents fail to import.

According to issues in the library github:

miku/esbulk#33

and the readme:

https://github.com/miku/esbulk?tab=readme-ov-file#esbulk

Using default settings might solve those errors. So far, it seems to
be working.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@miku @claytondukes