[
https://issues.apache.org/jira/browse/HBASE-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139293#comment-16139293
]
Enis Soztutar commented on HBASE-18432:
---
I don't understand the concerns here. You are right that
[
https://issues.apache.org/jira/browse/HBASE-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119262#comment-16119262
]
Hadoop QA commented on HBASE-18432:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote ||
[
https://issues.apache.org/jira/browse/HBASE-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110879#comment-16110879
]
stack commented on HBASE-18432:
---
bq. how to handle skews...
NTP? If not, lets take on this issue [~appy]
[
https://issues.apache.org/jira/browse/HBASE-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110127#comment-16110127
]
Appy commented on HBASE-18432:
--
Breaking out design changes in 001.patch into separate jira (HBASE-18498) so
[
https://issues.apache.org/jira/browse/HBASE-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099237#comment-16099237
]
Appy commented on HBASE-18432:
--
Quickly went through design doc attached in parent jira
[
https://issues.apache.org/jira/browse/HBASE-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097559#comment-16097559
]
stack commented on HBASE-18432:
---
On the solution:
bq. Keep track of skew in clock. And instead of keeping
[
https://issues.apache.org/jira/browse/HBASE-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097551#comment-16097551
]
stack commented on HBASE-18432:
---
On problem #1, 'That means, in worst case, our logical clock window should
[
https://issues.apache.org/jira/browse/HBASE-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097120#comment-16097120
]
Hadoop QA commented on HBASE-18432:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
