[
https://issues.apache.org/jira/browse/HBASE-16729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567682#comment-15567682
]
ramkrishna.s.vasudevan commented on HBASE-16729:
Better to revisit other
[
https://issues.apache.org/jira/browse/HBASE-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567696#comment-15567696
]
Hudson commented on HBASE-16663:
FAILURE: Integrated in Jenkins build HBase-1.4 #462 (See
[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567711#comment-15567711
]
Heng Chen commented on HBASE-16664:
---
OK. If all your guys agree with operation timeout
[
https://issues.apache.org/jira/browse/HBASE-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567731#comment-15567731
]
ChiaPing Tsai commented on HBASE-16801:
---
The scenario is extremely rare, but you ar
[
https://issues.apache.org/jira/browse/HBASE-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567734#comment-15567734
]
Hudson commented on HBASE-16663:
SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #45
[
https://issues.apache.org/jira/browse/HBASE-15561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567741#comment-15567741
]
ramkrishna.s.vasudevan commented on HBASE-15561:
I will close this JIRA l
[
https://issues.apache.org/jira/browse/HBASE-15561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan resolved HBASE-15561.
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.0.0
A
[
https://issues.apache.org/jira/browse/HBASE-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567753#comment-15567753
]
Hudson commented on HBASE-16663:
FAILURE: Integrated in Jenkins build HBase-1.3-JDK8 #43
[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Yang updated HBASE-16664:
--
Attachment: HBASE-16664-v6.patch
Fix race condition issue
> Timeout logic in AsyncProcess is broken
>
[
https://issues.apache.org/jira/browse/HBASE-16807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567756#comment-15567756
]
Pankaj Kumar commented on HBASE-16807:
--
Thanks [~stack], will upload the patch soon.
[
https://issues.apache.org/jira/browse/HBASE-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChiaPing Tsai reopened HBASE-16801:
---
address [~stack]'s comments.
> The Append/Increment may return the data from future
> --
[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Yang updated HBASE-16664:
--
Attachment: HBASE-16664-branch-1.1-v2.patch
> Timeout logic in AsyncProcess is broken
> ---
[
https://issues.apache.org/jira/browse/HBASE-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChiaPing Tsai updated HBASE-16801:
--
Attachment: HBASE-16801.v0.addendum.patch
> The Append/Increment may return the data from futur
[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Yang updated HBASE-16664:
--
Description: Rpc/operation timeout logic in AsyncProcess is broken. And
Table's set*Timeout does not ta
[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Yang updated HBASE-16664:
--
Attachment: (was: HBASE-16664-branch-1.1-v2.patch)
> Timeout logic in AsyncProcess is broken
>
[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567778#comment-15567778
]
Heng Chen commented on HBASE-16664:
---
it should be better for tracker.start() moved into
[
https://issues.apache.org/jira/browse/HBASE-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChiaPing Tsai updated HBASE-16801:
--
Attachment: HBASE-16801.branch-1.v0.patch
> The Append/Increment may return the data from futur
[
https://issues.apache.org/jira/browse/HBASE-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChiaPing Tsai updated HBASE-16801:
--
Status: Patch Available (was: Reopened)
> The Append/Increment may return the data from future
[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567813#comment-15567813
]
Phil Yang commented on HBASE-16664:
---
I think the start time should be the TS that user
[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567826#comment-15567826
]
Heng Chen commented on HBASE-16664:
---
As for operationTimeout meaning, yeah, the opera
[
https://issues.apache.org/jira/browse/HBASE-16731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567842#comment-15567842
]
ChiaPing Tsai commented on HBASE-16731:
---
[~ram_krish]
Yes, the feature should be ad
[
https://issues.apache.org/jira/browse/HBASE-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Yang updated HBASE-16664:
--
Attachment: HBASE-16664-v7.patch
Also call RetryingTimeTracker's start in HTable
> Timeout logic in As
201 - 222 of 222 matches
Mail list logo