[
https://issues.apache.org/jira/browse/HBASE-19731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317495#comment-16317495
]
Duo Zhang commented on HBASE-19731:
-----------------------------------
{quote}
Failing that, a timestamper like that in patch would be a limit of about 1k ops
a second?
{quote}
It is region level, and is only for write, so 1k ops per second is fast enough?
No? Since the problem only appears on row level, we can simply do a sharding?
For example, using 1024 AtomicLongs, then the qps limit can be up to 1M.
What do you think [~stack]?
Thanks.
> TestFromClientSide#testCheckAndDeleteWithCompareOp and testNullQualifier are
> flakey
> -----------------------------------------------------------------------------------
>
> Key: HBASE-19731
> URL: https://issues.apache.org/jira/browse/HBASE-19731
> Project: HBase
> Issue Type: Sub-task
> Components: test
> Reporter: stack
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19731.patch
>
>
> These two tests fail frequently locally; rare does this suite pass.
> The failures are either of these two tests. Unfortunately, running the test
> standalone does not bring on the issue; need to run the whole suite.
> In both cases, we have a Delete followed by a Put and then a checkAnd* -type
> operation which does a Get expecting to find the just put Put but it fails on
> occasion.
> Looks to be an mvcc issues or Put going in at same timestamp as the Delete.
> Its hard to debug given any added logging seems to make it all pass again.
> Seems this too is new in beta-1. Running tests against alpha-4 seem to pass.
> Doing a compare....
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
