[jira] [Commented] (HADOOP-16461) Regression: FileSystem cache lock parses XML within the lock

2019-07-24 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892278#comment-16892278 ] Gopal V commented on HADOOP-16461: -- Linked the lines up and opened a PR. > Regression: FileSystem

[jira] [Updated] (HADOOP-16461) Regression: FileSystem cache lock parses XML within the lock

2019-07-24 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-16461: - Description:

[jira] [Assigned] (HADOOP-16461) Regression: FileSystem cache lock parses XML within the lock

2019-07-24 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V reassigned HADOOP-16461: Assignee: Gopal V > Regression: FileSystem cache lock parses XML within the lock >

[jira] [Updated] (HADOOP-16461) Regression: FileSystem cache lock parses XML within the lock

2019-07-24 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-16461: - Description: {code} fs = createFileSystem(uri, conf); synchronized (this) { // refetch the

[jira] [Created] (HADOOP-16461) Regression: FileSystem cache lock parses XML within the lock

2019-07-24 Thread Gopal V (JIRA)
Gopal V created HADOOP-16461: Summary: Regression: FileSystem cache lock parses XML within the lock Key: HADOOP-16461 URL: https://issues.apache.org/jira/browse/HADOOP-16461 Project: Hadoop Common

[jira] [Commented] (HADOOP-16341) ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679

2019-06-03 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854936#comment-16854936 ] Gopal V commented on HADOOP-16341: -- Thanks, opened - https://github.com/apache/hadoop/pull/896 >

[jira] [Updated] (HADOOP-16341) ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679

2019-05-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-16341: - Attachment: HADOOP-16341.branch-3.1.002.patch > ShutDownHookManager: Regressed performance on Hook

[jira] [Commented] (HADOOP-16341) ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679

2019-05-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853594#comment-16853594 ] Gopal V commented on HADOOP-16341: -- Build failed for {code} [ERROR] bower qunit#1.19.0

[jira] [Updated] (HADOOP-16341) ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679

2019-05-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-16341: - Attachment: HADOOP-16341.branch-3.1.1.patch > ShutDownHookManager: Regressed performance on Hook

[jira] [Updated] (HADOOP-16341) ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679

2019-05-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-16341: - Fix Version/s: 3.1.3 Status: Patch Available (was: Open) > ShutDownHookManager: Regressed

[jira] [Updated] (HADOOP-16341) ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679

2019-05-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-16341: - Attachment: HADOOP-16341.1.patch > ShutDownHookManager: Regressed performance on Hook removals after

[jira] [Updated] (HADOOP-16341) ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679

2019-05-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-16341: - Attachment: (was: HADOOP-16341.1.patch) > ShutDownHookManager: Regressed performance on Hook

[jira] [Assigned] (HADOOP-16341) ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679

2019-05-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V reassigned HADOOP-16341: Assignee: Gopal V > ShutDownHookManager: Regressed performance on Hook removals after

[jira] [Created] (HADOOP-16341) ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679

2019-05-31 Thread Gopal V (JIRA)
Gopal V created HADOOP-16341: Summary: ShutDownHookManager: Regressed performance on Hook removals after HADOOP-15679 Key: HADOOP-16341 URL: https://issues.apache.org/jira/browse/HADOOP-16341 Project:

[jira] [Commented] (HADOOP-11223) Offer a read-only conf alternative to new Configuration()

2019-02-15 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769741#comment-16769741 ] Gopal V commented on HADOOP-11223: -- bq. Mainly for performance and concurrency reasons we don't want

[jira] [Updated] (HADOOP-11867) FS API: Add a high-performance vectored Read to FSDataInputStream API

2018-02-05 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11867: - Labels: performance (was: ) > FS API: Add a high-performance vectored Read to FSDataInputStream API >

[jira] [Updated] (HADOOP-11867) FS API: Add a high-performance vectored Read to FSDataInputStream API

2018-02-05 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11867: - Component/s: hdfs-client > FS API: Add a high-performance vectored Read to FSDataInputStream API >

[jira] [Updated] (HADOOP-11867) FS API: Add a high-performance vectored Read to FSDataInputStream API

2018-02-05 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11867: - Affects Version/s: (was: 2.8.0) 3.0.0 > FS API: Add a high-performance

[jira] [Commented] (HADOOP-11867) FS API: Add a high-performance vectored Read to FSDataInputStream API

2018-02-01 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349507#comment-16349507 ] Gopal V commented on HADOOP-11867: -- No, this is not about zero-copy readers or locality (i.e no Located

[jira] [Commented] (HADOOP-15171) Hadoop native ZLIB decompressor produces 0 bytes for some input

2018-01-29 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344204#comment-16344204 ] Gopal V commented on HADOOP-15171: -- bq. this is becoming a pain This is a huge perf hit right now,

[jira] [Comment Edited] (HADOOP-14683) FileStatus.compareTo binary compat issue between 2.7 and 2.8

2017-07-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100637#comment-16100637 ] Gopal V edited comment on HADOOP-14683 at 7/25/17 7:50 PM: --- bq. does this

[jira] [Comment Edited] (HADOOP-14683) FileStatus.compareTo binary compat issue between 2.7 and 2.8

2017-07-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100637#comment-16100637 ] Gopal V edited comment on HADOOP-14683 at 7/25/17 7:47 PM: --- bq. does this

[jira] [Comment Edited] (HADOOP-14683) FileStatus.compareTo binary compat issue between 2.7 and 2.8

2017-07-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100637#comment-16100637 ] Gopal V edited comment on HADOOP-14683 at 7/25/17 7:45 PM: --- bq. does this

[jira] [Commented] (HADOOP-14683) FileStatus.compareTo binary compat issue between 2.7 and 2.8

2017-07-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100637#comment-16100637 ] Gopal V commented on HADOOP-14683: -- bq. does this retain the binary search functionality? Yes - that's

[jira] [Commented] (HADOOP-14683) FileStatus.compareTo binary compat issue between 2.7 and 2.8

2017-07-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099608#comment-16099608 ] Gopal V commented on HADOOP-14683: -- [~ajisakaa]: use Comparable ? > FileStatus.compareTo binary compat

[jira] [Commented] (HADOOP-14054) NativeAzureFileSystem has multiple synchronized BufferedStream:read() calls in it

2017-02-03 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852088#comment-15852088 ] Gopal V commented on HADOOP-14054: -- thanks [~steve_l], I will probably link the external issues to this

[jira] [Resolved] (HADOOP-14054) NativeAzureFileSystem has multiple synchronized BufferedStream:read() calls in it

2017-02-03 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V resolved HADOOP-14054. -- Resolution: Won't Fix Closing as WONTFIX - will file issues on Azure github > NativeAzureFileSystem

[jira] [Created] (HADOOP-14054) NativeAzureFileSystem has multiple synchronized BufferedStream:read() calls in it

2017-02-03 Thread Gopal V (JIRA)
Gopal V created HADOOP-14054: Summary: NativeAzureFileSystem has multiple synchronized BufferedStream:read() calls in it Key: HADOOP-14054 URL: https://issues.apache.org/jira/browse/HADOOP-14054 Project:

[jira] [Commented] (HADOOP-12956) Inevitable Log4j2 migration via slf4j

2016-03-23 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209207#comment-15209207 ] Gopal V commented on HADOOP-12956: -- bq. if commons-logging supports log4j2.x LLAP moved DFSClient etc

[jira] [Created] (HADOOP-12956) Inevitable Log4j2 migration via slf4j

2016-03-22 Thread Gopal V (JIRA)
Gopal V created HADOOP-12956: Summary: Inevitable Log4j2 migration via slf4j Key: HADOOP-12956 URL: https://issues.apache.org/jira/browse/HADOOP-12956 Project: Hadoop Common Issue Type:

[jira] [Updated] (HADOOP-11771) Configuration::getClassByNameOrNull synchronizes on a static object

2015-11-13 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11771: - Description: {code} IPC Client (1970436060) connection to

[jira] [Updated] (HADOOP-11771) Configuration::getClassByNameOrNull synchronizes on a static object

2015-11-13 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11771: - Priority: Critical (was: Major) > Configuration::getClassByNameOrNull synchronizes on a static object

[jira] [Commented] (HADOOP-12444) Consider implementing lazy seek in S3AInputStream

2015-10-15 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960149#comment-14960149 ] Gopal V commented on HADOOP-12444: -- [~rajesh.balamohan]: Kicking off some 10Tb S3 tests with your

[jira] [Updated] (HADOOP-12444) Consider implementing lazy seek in S3AInputStream

2015-10-11 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-12444: - Assignee: Rajesh Subash > Consider implementing lazy seek in S3AInputStream >

[jira] [Updated] (HADOOP-12444) Consider implementing lazy seek in S3AInputStream

2015-10-11 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-12444: - Assignee: (was: Rajesh Subash) > Consider implementing lazy seek in S3AInputStream >

[jira] [Commented] (HADOOP-12217) hashCode in DoubleWritable returns same value for many numbers

2015-07-12 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14624087#comment-14624087 ] Gopal V commented on HADOOP-12217: -- bq. I would personally want to find out why fixing

[jira] [Commented] (HADOOP-12217) hashCode in DoubleWritable returns same value for many numbers

2015-07-10 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622817#comment-14622817 ] Gopal V commented on HADOOP-12217: -- [~sscaffidi]: I think I hit this earlier and

[jira] [Commented] (HADOOP-10694) Remove synchronized input streams from Writable deserialization

2015-07-09 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14621740#comment-14621740 ] Gopal V commented on HADOOP-10694: -- [~ozawa]: I think the synchronization is

[jira] [Assigned] (HADOOP-11867) FS API: Add a high-performance vectored Read to FSDataInputStream API

2015-06-16 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V reassigned HADOOP-11867: Assignee: Gopal V FS API: Add a high-performance vectored Read to FSDataInputStream API

[jira] [Updated] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-05-19 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11772: - Attachment: cached-locking.png cached-connections.png The patch looks good, there's no

[jira] [Commented] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-05-17 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547444#comment-14547444 ] Gopal V commented on HADOOP-11772: -- Added patch to next week's build + deploy queue.

[jira] [Commented] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-05-15 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546323#comment-14546323 ] Gopal V commented on HADOOP-11772: -- bq. reproduce the problem is to spawn a client that

[jira] [Commented] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-05-15 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546245#comment-14546245 ] Gopal V commented on HADOOP-11772: -- [~wheat9]: have you got any profiles on this with a

[jira] [Commented] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-05-15 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545934#comment-14545934 ] Gopal V commented on HADOOP-11772: -- bq. The RPC client will send out the request

[jira] [Commented] (HADOOP-11935) Provide optional native implementation of stat syscall.

2015-05-07 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14533063#comment-14533063 ] Gopal V commented on HADOOP-11935: -- [~cnauroth]:

[jira] [Commented] (HADOOP-11901) BytesWritable supports only up to ~700MB (instead of 2G) due to integer overflow.

2015-05-02 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14525437#comment-14525437 ] Gopal V commented on HADOOP-11901: -- If the only goal is overflow prevention you can

[jira] [Created] (HADOOP-11867) FS API: Add a high-performance vectored Read to FSDataInputStream API

2015-04-22 Thread Gopal V (JIRA)
Gopal V created HADOOP-11867: Summary: FS API: Add a high-performance vectored Read to FSDataInputStream API Key: HADOOP-11867 URL: https://issues.apache.org/jira/browse/HADOOP-11867 Project: Hadoop

[jira] [Commented] (HADOOP-11867) FS API: Add a high-performance vectored Read to FSDataInputStream API

2015-04-22 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507432#comment-14507432 ] Gopal V commented on HADOOP-11867: -- [~thodemoor]/[~sanjay.radia]: This is the

[jira] [Commented] (HADOOP-11867) FS API: Add a high-performance vectored Read to FSDataInputStream API

2015-04-22 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507569#comment-14507569 ] Gopal V commented on HADOOP-11867: -- bq. {{openAt(Path, offset)}} That is a good idea,

[jira] [Updated] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-04-08 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11772: - Attachment: after-ipc-fix.png [~ajisakaa]: looks much better with the patch. !after-ipc-fix.png! I

[jira] [Commented] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-04-07 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483923#comment-14483923 ] Gopal V commented on HADOOP-11772: -- [~ajisakaa]: added to today's builds. RPC Invoker

[jira] [Updated] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-03-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11772: - Attachment: dfs-sync-ipc.png [~ajisakaa]: Does this patch fix the requirement of needing 1 IPC client

[jira] [Updated] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-03-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11772: - Description: {code} private static ClientCache CLIENTS=new ClientCache(); ... this.client =

[jira] [Commented] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-03-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389056#comment-14389056 ] Gopal V commented on HADOOP-11772: -- bq. Do you mean we should create IPC client pool in

[jira] [Commented] (HADOOP-11771) Configuration::getClassByNameOrNull synchronizes on a static object

2015-03-28 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385168#comment-14385168 ] Gopal V commented on HADOOP-11771: -- The cache is of dubious value for the default

[jira] [Updated] (HADOOP-11770) [Umbrella] locate static synchronized blocks in hadoop-common

2015-03-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11770: - Priority: Critical (was: Major) [Umbrella] locate static synchronized blocks in hadoop-common

[jira] [Created] (HADOOP-11770) [Umbrella] locate static synchronized blocks in hadoop-common

2015-03-27 Thread Gopal V (JIRA)
Gopal V created HADOOP-11770: Summary: [Umbrella] locate static synchronized blocks in hadoop-common Key: HADOOP-11770 URL: https://issues.apache.org/jira/browse/HADOOP-11770 Project: Hadoop Common

[jira] [Updated] (HADOOP-11771) Configuration::getClassByNameOrNull synchronizes on a static object

2015-03-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11771: - Description: {code} private static final MapClassLoader, MapString, WeakReferenceClass?

[jira] [Updated] (HADOOP-11771) Configuration::getClassByNameOrNull synchronizes on a static object

2015-03-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11771: - Attachment: configuration-sync-cache.png configuration-cache-bt.png

[jira] [Created] (HADOOP-11771) Configuration::getClassByNameOrNull synchronizes on a static object

2015-03-27 Thread Gopal V (JIRA)
Gopal V created HADOOP-11771: Summary: Configuration::getClassByNameOrNull synchronizes on a static object Key: HADOOP-11771 URL: https://issues.apache.org/jira/browse/HADOOP-11771 Project: Hadoop Common

[jira] [Created] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-03-27 Thread Gopal V (JIRA)
Gopal V created HADOOP-11772: Summary: RPC Invoker relies on static ClientCache which has synchronized(this) blocks Key: HADOOP-11772 URL: https://issues.apache.org/jira/browse/HADOOP-11772 Project:

[jira] [Updated] (HADOOP-11772) RPC Invoker relies on static ClientCache which has synchronized(this) blocks

2015-03-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11772: - Attachment: sync-client-threads.png sync-client-bt.png RPC Invoker relies on static

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-03-09 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Status: Patch Available (was: Open) ipc.Client has to use setTrafficClass() with

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-03-09 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Attachment: HADOOP-11226.5.patch Updated patch with documentation ipc.Client has to use

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-03-09 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Status: Open (was: Patch Available) ipc.Client has to use setTrafficClass() with

[jira] [Commented] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-03-01 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14342523#comment-14342523 ] Gopal V commented on HADOOP-11226: -- Sure, I will add - I grepped to see where

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-02-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Status: Open (was: Patch Available) ipc.Client has to use setTrafficClass() with

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-02-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Status: Patch Available (was: Open) ipc.Client has to use setTrafficClass() with

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-02-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Attachment: HADOOP-11226.4.patch ipc.Client has to use setTrafficClass() with

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-02-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Status: Open (was: Patch Available) ipc.Client has to use setTrafficClass() with

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-02-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Status: Patch Available (was: Open) No added tests, since this has no easy way to test without a

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-02-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Attachment: HADOOP-11226.3.patch Added {{ipc.client.low-latency}} with default=false ipc.Client has

[jira] [Commented] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-02-22 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333052#comment-14333052 ] Gopal V commented on HADOOP-11226: -- Sure, I will update the patch in a couple of days

[jira] [Commented] (HADOOP-11223) Offer a read-only conf alternative to new Configuration()

2015-01-26 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14292452#comment-14292452 ] Gopal V commented on HADOOP-11223: -- [~cmccabe]: Agree, the current patch doesn't fix

[jira] [Commented] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-01-23 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14290067#comment-14290067 ] Gopal V commented on HADOOP-11226: -- Thanks [~cnauroth]. I think this needs testing

[jira] [Commented] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-01-22 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14287167#comment-14287167 ] Gopal V commented on HADOOP-11226: -- I was following the line which had TCP keepalive

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2015-01-20 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Labels: Infiniband (was: ) Release Note: Use low latency TCP connections for hadoop IPC

[jira] [Commented] (HADOOP-11449) Cannot build on Windows: error: unexpected end tag: /ul

2014-12-26 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14258986#comment-14258986 ] Gopal V commented on HADOOP-11449: -- This is not a windows error - this is bad HTML in

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2014-10-28 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Attachment: HADOOP-11226.2.patch ipc.Client has to use setTrafficClass() with

[jira] [Resolved] (HADOOP-11239) [JDK8] azurenative tests fail builds on JDK8

2014-10-28 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V resolved HADOOP-11239. -- Resolution: Not a Problem [JDK8] azurenative tests fail builds on JDK8

[jira] [Commented] (HADOOP-11223) Offer a read-only conf alternative to new Configuration()

2014-10-27 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14185990#comment-14185990 ] Gopal V commented on HADOOP-11223: -- Yes, that's the whole idea. This is merely from a

[jira] [Created] (HADOOP-11239) [JDK8] azurenative tests fail builds on JDK8

2014-10-27 Thread Gopal V (JIRA)
Gopal V created HADOOP-11239: Summary: [JDK8] azurenative tests fail builds on JDK8 Key: HADOOP-11239 URL: https://issues.apache.org/jira/browse/HADOOP-11239 Project: Hadoop Common Issue Type:

[jira] [Created] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY

2014-10-24 Thread Gopal V (JIRA)
Gopal V created HADOOP-11226: Summary: ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY Key: HADOOP-11226 URL: https://issues.apache.org/jira/browse/HADOOP-11226 Project: Hadoop Common

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY

2014-10-24 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Component/s: ipc Description: During heavy shuffle, packet loss for IPC packets was

[jira] [Assigned] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2014-10-24 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V reassigned HADOOP-11226: Assignee: Gopal V ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2014-10-24 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Summary: ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY (was:

[jira] [Updated] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2014-10-24 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11226: - Attachment: HADOOP-11226.1.patch ipc.Client has to use setTrafficClass() with

[jira] [Commented] (HADOOP-11226) ipc.Client has to use setTrafficClass() with IPTOS_LOWDELAY|IPTOS_RELIABILITY

2014-10-24 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183665#comment-14183665 ] Gopal V commented on HADOOP-11226: -- Patch is not complete, as it takes care of only RFC

[jira] [Created] (HADOOP-11223) Offer a read-only conf alternative to new Configuration()

2014-10-23 Thread Gopal V (JIRA)
Gopal V created HADOOP-11223: Summary: Offer a read-only conf alternative to new Configuration() Key: HADOOP-11223 URL: https://issues.apache.org/jira/browse/HADOOP-11223 Project: Hadoop Common

[jira] [Updated] (HADOOP-11223) Offer a read-only conf alternative to new Configuration()

2014-10-23 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11223: - Component/s: conf Offer a read-only conf alternative to new Configuration()

[jira] [Commented] (HADOOP-11144) Update website to reflect that we use git, not svn

2014-09-26 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14150110#comment-14150110 ] Gopal V commented on HADOOP-11144: -- Also retire broken mirrors -

[jira] [Updated] (HADOOP-11029) FileSystem#Statistics uses volatile variables that must be updated on write or read calls.

2014-09-08 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11029: - Attachment: fsdatainputstream.png FileSystem#Statistics uses volatile variables that must be updated

[jira] [Updated] (HADOOP-11029) FileSystem#Statistics uses volatile variables that must be updated on write or read calls.

2014-09-08 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11029: - Attachment: (was: fsdatainputstream.png) FileSystem#Statistics uses volatile variables that must

[jira] [Commented] (HADOOP-11029) FileSystem#Statistics uses volatile variables that must be updated on write or read calls.

2014-09-08 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126228#comment-14126228 ] Gopal V commented on HADOOP-11029: -- bq. Can you put some numbers behind this? If this

[jira] [Updated] (HADOOP-11029) FileSystem#Statistics uses volatile variables that must be updated on write or read calls.

2014-09-08 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11029: - Attachment: fsdatainputstream.png FileSystem#Statistics uses volatile variables that must be updated

[jira] [Updated] (HADOOP-11029) LocalFS Statistics performs thread local call per byte written

2014-08-29 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11029: - Affects Version/s: 2.6.0 2.5.0 LocalFS Statistics performs thread local call

[jira] [Created] (HADOOP-11029) LocalFS Statistics performs thread local call per byte written

2014-08-29 Thread Gopal V (JIRA)
Gopal V created HADOOP-11029: Summary: LocalFS Statistics performs thread local call per byte written Key: HADOOP-11029 URL: https://issues.apache.org/jira/browse/HADOOP-11029 Project: Hadoop Common

[jira] [Updated] (HADOOP-11029) LocalFS Statistics performs thread local call per byte written

2014-08-29 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11029: - Attachment: local-fs-locking.png LocalFS Statistics performs thread local call per byte written

[jira] [Updated] (HADOOP-11029) LocalFS Statistics performs thread local call per byte written

2014-08-29 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-11029: - Component/s: fs LocalFS Statistics performs thread local call per byte written

[jira] [Updated] (HADOOP-9601) Support native CRC on byte arrays

2014-08-18 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated HADOOP-9601: Resolution: Incomplete Status: Resolved (was: Patch Available) Closing this issue. btw, I found

  1   2   3   >