[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478976#comment-16478976
]
Hudson commented on HBASE-20520:
Results for branch master
[build #334 on
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478203#comment-16478203
]
Hudson commented on HBASE-20520:
Results for branch branch-2.0
[build #309 on
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478197#comment-16478197
]
Hudson commented on HBASE-20520:
Results for branch branch-2
[build #744 on
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477593#comment-16477593
]
Mike Drob commented on HBASE-20520:
---
[~stack] - any activity here?
> Failed effort upping default HDFS
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471187#comment-16471187
]
Mike Drob commented on HBASE-20520:
---
Left a minor nit on RB, otherwise patch looks good. +1 to commit
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462036#comment-16462036
]
ramkrishna.s.vasudevan commented on HBASE-20520:
bq.Example please ramkrishna.s.vasudevan
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461893#comment-16461893
]
stack commented on HBASE-20520:
---
Thanks [~mdrob] I got a little lost in the hierarchy here. We should do a
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461842#comment-16461842
]
Mike Drob commented on HBASE-20520:
---
change makes sense, v5 LGTM.
+1 assuming QA is happy.
> Failed
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461821#comment-16461821
]
stack commented on HBASE-20520:
---
.005 Edit. Fix test.
> Failed effort upping default HDFS blocksize,
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461702#comment-16461702
]
Hadoop QA commented on HBASE-20520:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461604#comment-16461604
]
stack commented on HBASE-20520:
---
Add test to verify default takes in both WAL providers. Let me see how
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461560#comment-16461560
]
Hadoop QA commented on HBASE-20520:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461468#comment-16461468
]
stack commented on HBASE-20520:
---
bq. You think the too-early log roll maybe had perf impact on our write
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461427#comment-16461427
]
ramkrishna.s.vasudevan commented on HBASE-20520:
In the logs I noticed that WAL A gets
[
https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461416#comment-16461416
]
Mike Drob commented on HBASE-20520:
---
You think the too-early log roll maybe had perf impact on our
15 matches
Mail list logo