[jira] [Commented] (HBASE-9393) Hbase does not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105939#comment-15105939 ] Colin Patrick McCabe commented on HBASE-9393: - Unfortunately, this is kind of a complex topic.

[jira] [Commented] (HBASE-9393) Hbase does not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102383#comment-15102383 ] Colin Patrick McCabe commented on HBASE-9393: - The timeout that I'm talking about is inside

[jira] [Commented] (HBASE-9393) Hbase does not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098796#comment-15098796 ] Colin Patrick McCabe commented on HBASE-9393: - The client should be configured so that it

[jira] [Updated] (HBASE-14451) Move on to htrace-4.0.1 (from htrace-3.2.0)

[ https://issues.apache.org/jira/browse/HBASE-14451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HBASE-14451: - Summary: Move on to htrace-4.0.1 (from htrace-3.2.0) (was: Move on to

[jira] [Commented] (HBASE-14451) Move on to htrace-4.0.0 (from htrace-3.2.0)

[ https://issues.apache.org/jira/browse/HBASE-14451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903324#comment-14903324 ] Colin Patrick McCabe commented on HBASE-14451: -- Thanks for this, [~stack].

[jira] [Commented] (HBASE-14451) Move on to htrace-4.0.0 (from htrace-3.2.0)

[ https://issues.apache.org/jira/browse/HBASE-14451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14901651#comment-14901651 ] Colin Patrick McCabe commented on HBASE-14451: -- [~stack]: right, to get "cross-cutting"

[jira] [Commented] (HBASE-9393) Hbase does not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14535512#comment-14535512 ] Colin Patrick McCabe commented on HBASE-9393: - CDH4.4 had some configuration

[jira] [Created] (HBASE-13060) Don't use deprecated HTrace API addKVAnnotation(byte[], byte[])

Colin Patrick McCabe created HBASE-13060: Summary: Don't use deprecated HTrace API addKVAnnotation(byte[], byte[]) Key: HBASE-13060 URL: https://issues.apache.org/jira/browse/HBASE-13060

[jira] [Commented] (HBASE-13060) Don't use deprecated HTrace API addKVAnnotation(byte[], byte[])

[ https://issues.apache.org/jira/browse/HBASE-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14324981#comment-14324981 ] Colin Patrick McCabe commented on HBASE-13060: -- It looks like the

[jira] [Updated] (HBASE-12899) HBase should prefix htrace configuration keys with hbase.htrace rather than just hbase.

[ https://issues.apache.org/jira/browse/HBASE-12899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HBASE-12899: - Status: Patch Available (was: Open) HBase should prefix htrace configuration

[jira] [Created] (HBASE-12899) HBase should prefix htrace configuration keys with hbase.htrace rather than just hbase.

Colin Patrick McCabe created HBASE-12899: Summary: HBase should prefix htrace configuration keys with hbase.htrace rather than just hbase. Key: HBASE-12899 URL:

[jira] [Commented] (HBASE-12899) HBase should prefix htrace configuration keys with hbase.htrace rather than just hbase.

[ https://issues.apache.org/jira/browse/HBASE-12899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14286476#comment-14286476 ] Colin Patrick McCabe commented on HBASE-12899: -- thanks for the review, Nick.

[jira] [Updated] (HBASE-12899) HBase should prefix htrace configuration keys with hbase.htrace rather than just hbase.

[ https://issues.apache.org/jira/browse/HBASE-12899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HBASE-12899: - Attachment: HBASE-12899.002.patch OK. We can set the new configuration keys

[jira] [Updated] (HBASE-12899) HBase should prefix htrace configuration keys with hbase.htrace rather than just hbase.

[ https://issues.apache.org/jira/browse/HBASE-12899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HBASE-12899: - Attachment: HBASE-12899.001.patch HBase should prefix htrace configuration keys

[jira] [Commented] (HBASE-9393) Hbase does not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118943#comment-14118943 ] Colin Patrick McCabe commented on HBASE-9393: - Best guess is that you didn't

[jira] [Commented] (HBASE-10689) Explore advisory caching for MR over snapshot scans

[ https://issues.apache.org/jira/browse/HBASE-10689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13926010#comment-13926010 ] Colin Patrick McCabe commented on HBASE-10689: -- No problem. I agree it can

[jira] [Commented] (HBASE-10689) Explore advisory caching for MR over snapshot scans

[ https://issues.apache.org/jira/browse/HBASE-10689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925386#comment-13925386 ] Colin Patrick McCabe commented on HBASE-10689: -- [~stack], there are multiple

[jira] [Commented] (HBASE-10052) use HDFS advisory caching to avoid caching HFiles that are not going to be read again (because they are being compacted)

[ https://issues.apache.org/jira/browse/HBASE-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840355#comment-13840355 ] Colin Patrick McCabe commented on HBASE-10052: -- bq. One thing to be wary of:

[jira] [Commented] (HBASE-10052) use HDFS advisory caching to avoid caching HFiles that are not going to be read again (because they are being compacted)

[ https://issues.apache.org/jira/browse/HBASE-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13838543#comment-13838543 ] Colin Patrick McCabe commented on HBASE-10052: -- [~enis] It would be

[jira] [Created] (HBASE-10052) use HDFS advisory caching to avoid caching HFiles that are not going to be read again (because they are being compacted)

Colin Patrick McCabe created HBASE-10052: Summary: use HDFS advisory caching to avoid caching HFiles that are not going to be read again (because they are being compacted) Key: HBASE-10052 URL:

[jira] [Commented] (HBASE-10052) use HDFS advisory caching to avoid caching HFiles that are not going to be read again (because they are being compacted)

[ https://issues.apache.org/jira/browse/HBASE-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834203#comment-13834203 ] Colin Patrick McCabe commented on HBASE-10052: -- [~andrew.purt...@gmail.com]

[jira] [Updated] (HBASE-10052) use HDFS advisory caching to avoid caching HFiles that are not going to be read again (because they are being compacted)

[ https://issues.apache.org/jira/browse/HBASE-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HBASE-10052: - Description: HBase can benefit from doing dropbehind during compaction since

[jira] [Commented] (HBASE-10052) use HDFS advisory caching to avoid caching HFiles that are not going to be read again (because they are being compacted)

[ https://issues.apache.org/jira/browse/HBASE-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834477#comment-13834477 ] Colin Patrick McCabe commented on HBASE-10052: -- [~andrew.purt...@gmail.com]

[jira] [Commented] (HBASE-9393) Hbase dose not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13792915#comment-13792915 ] Colin Patrick McCabe commented on HBASE-9393: - I looked into this issue. I

[jira] [Commented] (HBASE-9393) Hbase dose not closing a closed socket resulting in many CLOSE_WAIT

[ https://issues.apache.org/jira/browse/HBASE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13792938#comment-13792938 ] Colin Patrick McCabe commented on HBASE-9393: - I guess I should also explain

[jira] [Commented] (HBASE-8337) Investigate why disabling hadoop short circuit read is required to make recovery tests pass consistently under hadoop2

[ https://issues.apache.org/jira/browse/HBASE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640976#comment-13640976 ] Colin Patrick McCabe commented on HBASE-8337: - bq. Looks like this has allowed

[jira] [Commented] (HBASE-8337) Investigate why disabling hadoop short circuit read is required to make recovery tests pass consistently under hadoop2

[ https://issues.apache.org/jira/browse/HBASE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641069#comment-13641069 ] Colin Patrick McCabe commented on HBASE-8337: - bq. Maybe I'm missing it in the

[jira] [Commented] (HBASE-8337) Investigate why disabling hadoop short circuit read is required to make recovery tests pass consistently under hadoop2

[ https://issues.apache.org/jira/browse/HBASE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13639970#comment-13639970 ] Colin Patrick McCabe commented on HBASE-8337: - Actually, the 2.0 series will

[jira] [Commented] (HBASE-8337) Investigate why disabling hadoop short circuit read is required to make recovery tests pass consistently under hadoop2

[ https://issues.apache.org/jira/browse/HBASE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632467#comment-13632467 ] Colin Patrick McCabe commented on HBASE-8337: - It's good to have HDFS-347

[jira] [Commented] (HBASE-7636) TestDistributedLogSplitting#testThreeRSAbort fails against hadoop 2.0

[ https://issues.apache.org/jira/browse/HBASE-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13630453#comment-13630453 ] Colin Patrick McCabe commented on HBASE-7636: - I was not able to find any HDFS

[jira] [Commented] (HBASE-7636) TestDistributedLogSplitting#testThreeRSAbort fails against hadoop 2.0

[ https://issues.apache.org/jira/browse/HBASE-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13630477#comment-13630477 ] Colin Patrick McCabe commented on HBASE-7636: - bq. Is HDFS-347 the new