[
https://issues.apache.org/jira/browse/HBASE-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150971#comment-14150971
]
stack commented on HBASE-12075:
-------------------------------
[~manukranthk] It is tricky to find. We should make it easier by publishing
the javadoc warnings in list of urls. To find the javadoc warnings, you need
to navigate to the build artifacts for your patch build. Take one of the urls
above and chop off the last bit as in take:
https://builds.apache.org/job/PreCommit-HBASE-Build/11112//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
and remove the last bit to get
https://builds.apache.org/job/PreCommit-HBASE-Build/11112//artifact/patchprocess/
You'll see a long list including javadoc warnings pages....
including this one....
https://builds.apache.org/job/PreCommit-HBASE-Build/11112//artifact/patchprocess/patchJavadocWarnings.txt
Grep for WARNING
Ignore the ones that are obviously not yours (e.g. the Unsafe WARNINGs)....
There seem to be some that belong to you if you keep grepping down...
> Preemptive Fast Fail
> --------------------
>
> Key: HBASE-12075
> URL: https://issues.apache.org/jira/browse/HBASE-12075
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Affects Versions: 1.0.0
> Reporter: Manukranth Kolloju
> Assignee: Manukranth Kolloju
> Fix For: 1.0.0
>
> Attachments: 0001-Add-a-test-case-for-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch
>
>
> In multi threaded clients, we use a feature developed on 0.89-fb branch
> called Preemptive Fast Fail. This allows the client threads which would
> potentially fail, fail fast. The idea behind this feature is that we allow,
> among the hundreds of client threads, one thread to try and establish
> connection with the regionserver and if that succeeds, we mark it as a live
> node again. Meanwhile, other threads which are trying to establish connection
> to the same server would ideally go into the timeouts which is effectively
> unfruitful. We can in those cases return appropriate exceptions to those
> clients instead of letting them retry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
