Closed namper closed 7 months ago
Hey! There are currently 2 ways to do bulk verification:
/v0/bulk
endpoints as you did. This bulk will send the jobs to the Postgres DB. Apparently it's bugged, as you reported.I'm planning to remove support for 1. There's a too big dependency on https://github.com/Diggsey/sqlxmq, whereas RabbitMQ is battle-tested and performant (and running on Reacher in production for 1 month).
As such, I'll mark this issue as wont-fix, and work instead on adding docs to the RabbitMQ-based bulk.
For now, if you want to try RabbitMQ-based bulk, you'll need to mostly play around yourself:
RCH_AMQP_ADDR=<rabbitmq address> cargo run --features=worker --bin reacher_backend
Not super friendly for external contributors for now, but I'll work on adding docs in the next few weeks.
Thanks for the response, It would be great to have some client friendly bulk api in future. I am not expert in rust/warp but happy to contribute.
Email to check
No response
From where did you run check-if-email-exists?
Local, AWS EC2
Version of check-if-email-exists (if running it yourself)
0.9.1
What happened?
Bulk job is in running state forever. In logs, task UUIDs are returned successfully, However /v0/bulk/7 status is running for quite long time.
Relevant log output
I have Postgres and RabbitMQ running, data is saved to Postgres. Did I miss a setup step for this ?