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.

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

Mixed Workloads (Read,Write,Delete) cause low read success rate. #254

Closed
nakleppa opened this issue Mar 9, 2015 · 1 comment
Closed

Comments

@nakleppa
Copy link

nakleppa commented Mar 9, 2015

Running a workload with a mix of reads, writes, and delete operations in the same workstage causes Cosbench to have an extremely low success ratio for read operations. Logs indicate that this is due to 404 not found errors. Given that the only success ratio affected is the reads, it is suspected that the deleted objects are not being removed from the list of objects available for access.

@ywang19
Copy link
Contributor

ywang19 commented Mar 18, 2015

if you set read/write/delete working on the container range, object range, yes, you will see low success ratio for read, as many objects may be deleted when read.
to mix those operations in one work, a normal approach is to set operators working on isolated container/object range to avoid confliction. e.g,
read: container [1,10], write: container [11,20], delete: container [21,30].

@ywang19 ywang19 closed this as completed Apr 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants