[jira] [Commented] (HADOOP-17161) Make ipc.Client.stop() sleep configurable

2020-07-30 Thread Ramesh Kumar Thangarajan (Jira)


[ 
https://issues.apache.org/jira/browse/HADOOP-17161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17168172#comment-17168172
 ] 

Ramesh Kumar Thangarajan commented on HADOOP-17161:
---

It is low latency hive queries running less than a second.

> Make ipc.Client.stop() sleep configurable
> -
>
> Key: HADOOP-17161
> URL: https://issues.apache.org/jira/browse/HADOOP-17161
> Project: Hadoop Common
>  Issue Type: Bug
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
>
> After identifying HADOOP-16126 might cause issues in few workloads, 
> ipc.Client.stop() sleep was identified to be configurable to better suit 
> multiple workloads



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Created] (HADOOP-17161) Make ipc.Client.stop() sleep configurable

2020-07-27 Thread Ramesh Kumar Thangarajan (Jira)
Ramesh Kumar Thangarajan created HADOOP-17161:
-

 Summary: Make ipc.Client.stop() sleep configurable
 Key: HADOOP-17161
 URL: https://issues.apache.org/jira/browse/HADOOP-17161
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Ramesh Kumar Thangarajan


After identifying HADOOP-16126 might cause issues in few workloads, 
ipc.Client.stop() sleep was identified to be configurable to better suit 
multiple workloads



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-17048) Increase number of IPC calls and lock creating contention for low latency queries

2020-06-15 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-17048:
--
Attachment: HADOOP-17048.1.patch
Status: Patch Available  (was: Open)

> Increase number of IPC calls and lock creating contention for low latency 
> queries
> -
>
> Key: HADOOP-17048
> URL: https://issues.apache.org/jira/browse/HADOOP-17048
> Project: Hadoop Common
>  Issue Type: Bug
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-17048.1.patch
>
>
> After HADOOP-16126 and HADOOP-16127, we noticed lock issues even in local FS, 
> caused by IPC
> "Task-Executor-11" #273 daemon prio=5 os_prio=0 tid=0x7fe204664800 
> nid=0x2343d2 waiting on condition [0x7fe1fcfda000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
>   at java.lang.Thread.sleep(Native Method)
>   at org.apache.hadoop.ipc.Client.stop(Client.java:1329)
>   at org.apache.hadoop.ipc.ClientCache.stopClient(ClientCache.java:113)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.close(ProtobufRpcEngine.java:302)
>   at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:677)
>   at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.close(ClientNamenodeProtocolTranslatorPB.java:304)
>   at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:672)
>   at 
> [org.apache.hadoop.io|http://org.apache.hadoop.io/]
> .retry.DefaultFailoverProxyProvider.close(DefaultFailoverProxyProvider.java:57)
>   at 
> [org.apache.hadoop.io|http://org.apache.hadoop.io/]
> .retry.RetryInvocationHandler$ProxyDescriptor.close(RetryInvocationHandler.java:234)
>   at 
> [org.apache.hadoop.io|http://org.apache.hadoop.io/]
> .retry.RetryInvocationHandler.close(RetryInvocationHandler.java:444)
>   at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:677)
>   at 
> org.apache.hadoop.hdfs.DFSClient.closeConnectionToNamenode(DFSClient.java:592)
>   at org.apache.hadoop.hdfs.DFSClient.close(DFSClient.java:633)
>   - locked <0x7fed071063a0> (a org.apache.hadoop.hdfs.DFSClient)
>   at 
> org.apache.hadoop.hdfs.DistributedFileSystem.close(DistributedFileSystem.java:1358)
>   at org.apache.hadoop.fs.FileSystem$Cache.closeAll(FileSystem.java:3463)
>   - locked <0x7fe63d00> (a org.apache.hadoop.fs.FileSystem$Cache)
>   at org.apache.hadoop.fs.FileSystem.closeAllForUGI(FileSystem.java:576)
>   at 
> org.apache.hadoop.hive.llap.daemon.impl.TaskRunnerCallable.callInternal(TaskRunnerCallable.java:299)
>   at 
> org.apache.hadoop.hive.llap.daemon.impl.TaskRunnerCallable.callInternal(TaskRunnerCallable.java:93)
>   at org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36)
>   at 
> com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:108)
>   at 
> com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:41)
>   at 
> com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:77)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)"New I/O worker #44" #80 prio=5 
> os_prio=0 tid=0x7fede2a03000 nid=0x233f2b waiting for monitor entry 
> [0x7fe20cd3d000]
>java.lang.Thread.State: BLOCKED (on object monitor)
>   at 
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3345)
>   - waiting to lock <0x7fe63d00> (a 
> org.apache.hadoop.fs.FileSystem$Cache)
>   at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3320)
>   at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:479)
>   at org.apache.hadoop.fs.FileSystem.getLocal(FileSystem.java:435)
>   at 
> org.apache.tez.runtime.library.common.sort.impl.TezSpillRecord.(TezSpillRecord.java:65)
>   at 
> org.apache.tez.runtime.library.common.sort.impl.TezSpillRecord.(TezSpillRecord.java:58)
>   at 
> org.apache.hadoop.hive.llap.shufflehandler.IndexCache.readIndexFileToCache(IndexCache.java:121)
>   at 
> org.apache.hadoop.hive.llap.shufflehandler.IndexCache.getIndexInformation(IndexCache.java:70)
>   at 
> org.apache.hadoop.hive.llap.shufflehandler.ShuffleHandler$Shuffle.getMapOutputInfo(ShuffleHandler.java:887)
>   at 
> org.apache.hadoop.hive.llap.shufflehandler.ShuffleHandler$Shuffle.populateHeaders(ShuffleHandler.java:908)
>   at 
> org.apache.hadoop.hive.llap.shufflehandler.ShuffleHandler$Shuffle.messageReceived(ShuffleHandler.java:805)
>   at 
> 

[jira] [Created] (HADOOP-17048) Increase number of IPC calls and lock creating contention for low latency queries

2020-05-18 Thread Ramesh Kumar Thangarajan (Jira)
Ramesh Kumar Thangarajan created HADOOP-17048:
-

 Summary: Increase number of IPC calls and lock creating contention 
for low latency queries
 Key: HADOOP-17048
 URL: https://issues.apache.org/jira/browse/HADOOP-17048
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Ramesh Kumar Thangarajan


After HADOOP-16126 and HADOOP-16127, we noticed lock issues even in local FS, 
caused by IPC

"Task-Executor-11" #273 daemon prio=5 os_prio=0 tid=0x7fe204664800 
nid=0x2343d2 waiting on condition [0x7fe1fcfda000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at org.apache.hadoop.ipc.Client.stop(Client.java:1329)
at org.apache.hadoop.ipc.ClientCache.stopClient(ClientCache.java:113)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.close(ProtobufRpcEngine.java:302)
at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:677)
at 
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.close(ClientNamenodeProtocolTranslatorPB.java:304)
at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:672)
at 
[org.apache.hadoop.io|http://org.apache.hadoop.io/]
.retry.DefaultFailoverProxyProvider.close(DefaultFailoverProxyProvider.java:57)
at 
[org.apache.hadoop.io|http://org.apache.hadoop.io/]
.retry.RetryInvocationHandler$ProxyDescriptor.close(RetryInvocationHandler.java:234)
at 
[org.apache.hadoop.io|http://org.apache.hadoop.io/]
.retry.RetryInvocationHandler.close(RetryInvocationHandler.java:444)
at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:677)
at 
org.apache.hadoop.hdfs.DFSClient.closeConnectionToNamenode(DFSClient.java:592)
at org.apache.hadoop.hdfs.DFSClient.close(DFSClient.java:633)
- locked <0x7fed071063a0> (a org.apache.hadoop.hdfs.DFSClient)
at 
org.apache.hadoop.hdfs.DistributedFileSystem.close(DistributedFileSystem.java:1358)
at org.apache.hadoop.fs.FileSystem$Cache.closeAll(FileSystem.java:3463)
- locked <0x7fe63d00> (a org.apache.hadoop.fs.FileSystem$Cache)
at org.apache.hadoop.fs.FileSystem.closeAllForUGI(FileSystem.java:576)
at 
org.apache.hadoop.hive.llap.daemon.impl.TaskRunnerCallable.callInternal(TaskRunnerCallable.java:299)
at 
org.apache.hadoop.hive.llap.daemon.impl.TaskRunnerCallable.callInternal(TaskRunnerCallable.java:93)
at org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36)
at 
com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:108)
at 
com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:41)
at 
com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:77)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)"New I/O worker #44" #80 prio=5 
os_prio=0 tid=0x7fede2a03000 nid=0x233f2b waiting for monitor entry 
[0x7fe20cd3d000]
   java.lang.Thread.State: BLOCKED (on object monitor)
at 
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3345)
- waiting to lock <0x7fe63d00> (a 
org.apache.hadoop.fs.FileSystem$Cache)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3320)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:479)
at org.apache.hadoop.fs.FileSystem.getLocal(FileSystem.java:435)
at 
org.apache.tez.runtime.library.common.sort.impl.TezSpillRecord.(TezSpillRecord.java:65)
at 
org.apache.tez.runtime.library.common.sort.impl.TezSpillRecord.(TezSpillRecord.java:58)
at 
org.apache.hadoop.hive.llap.shufflehandler.IndexCache.readIndexFileToCache(IndexCache.java:121)
at 
org.apache.hadoop.hive.llap.shufflehandler.IndexCache.getIndexInformation(IndexCache.java:70)
at 
org.apache.hadoop.hive.llap.shufflehandler.ShuffleHandler$Shuffle.getMapOutputInfo(ShuffleHandler.java:887)
at 
org.apache.hadoop.hive.llap.shufflehandler.ShuffleHandler$Shuffle.populateHeaders(ShuffleHandler.java:908)
at 
org.apache.hadoop.hive.llap.shufflehandler.ShuffleHandler$Shuffle.messageReceived(ShuffleHandler.java:805)
at 
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
at 
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at 
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
at 

[jira] [Commented] (HADOOP-16769) LocalDirAllocator to provide diagnostics when file creation fails

2020-03-11 Thread Ramesh Kumar Thangarajan (Jira)


[ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056743#comment-17056743
 ] 

Ramesh Kumar Thangarajan commented on HADOOP-16769:
---

[~gabor.bota] I have addressed the comments in the old PR. Can you please help 
review the new PR at [https://github.com/apache/hadoop/pull/1892/files]?

 

> LocalDirAllocator to provide diagnostics when file creation fails
> -
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: util
>Reporter: Ramesh Kumar Thangarajan
>Priority: Minor
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch, HADOOP-16769.6.patch, 
> HADOOP-16769.7.patch, HADOOP-16769.8.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Comment Edited] (HADOOP-16769) LocalDirAllocator to provide diagnostics when file creation fails

2020-03-09 Thread Ramesh Kumar Thangarajan (Jira)


[ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055123#comment-17055123
 ] 

Ramesh Kumar Thangarajan edited comment on HADOOP-16769 at 3/9/20, 4:03 PM:


[~amagyar] [~gabor.bota] I got this missed. I have the patch already. I have 
addressed the comments in PR, uploaded a new patch now, I will wait for a green 
test run and update the PR.


was (Author: rameshkumar):
[~amagyar] [~gabor.bota] I got this missed. I have the patch already. I have 
addressed the comments in PR, I will wait for a green test run and update the 
PR.

> LocalDirAllocator to provide diagnostics when file creation fails
> -
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: util
>Reporter: Ramesh Kumar Thangarajan
>Priority: Minor
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch, HADOOP-16769.6.patch, 
> HADOOP-16769.7.patch, HADOOP-16769.8.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Commented] (HADOOP-16769) LocalDirAllocator to provide diagnostics when file creation fails

2020-03-09 Thread Ramesh Kumar Thangarajan (Jira)


[ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055123#comment-17055123
 ] 

Ramesh Kumar Thangarajan commented on HADOOP-16769:
---

[~amagyar] [~gabor.bota] I got this missed. I have the patch already. I have 
addressed the comments in PR, I will wait for a green test run and update the 
PR.

> LocalDirAllocator to provide diagnostics when file creation fails
> -
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: util
>Reporter: Ramesh Kumar Thangarajan
>Priority: Minor
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch, HADOOP-16769.6.patch, 
> HADOOP-16769.7.patch, HADOOP-16769.8.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) LocalDirAllocator to provide diagnostics when file creation fails

2020-03-09 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Attachment: HADOOP-16769.8.patch
Status: Patch Available  (was: Open)

> LocalDirAllocator to provide diagnostics when file creation fails
> -
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: util
>Reporter: Ramesh Kumar Thangarajan
>Priority: Minor
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch, HADOOP-16769.6.patch, 
> HADOOP-16769.7.patch, HADOOP-16769.8.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) LocalDirAllocator to provide diagnostics when file creation fails

2020-03-09 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Status: Open  (was: Patch Available)

> LocalDirAllocator to provide diagnostics when file creation fails
> -
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: util
>Reporter: Ramesh Kumar Thangarajan
>Priority: Minor
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch, HADOOP-16769.6.patch, 
> HADOOP-16769.7.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Resolved] (HADOOP-16831) Boundary condition to check if there is nothing to truncate in StringExpr functions

2020-01-27 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan resolved HADOOP-16831.
---
Resolution: Abandoned

> Boundary condition to check if there is nothing to truncate in StringExpr 
> functions
> ---
>
> Key: HADOOP-16831
> URL: https://issues.apache.org/jira/browse/HADOOP-16831
> Project: Hadoop Common
>  Issue Type: Bug
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
>
> Add a boundary condition to check if there is nothing to truncate in 
> StringExpr functions
> truncate()
> rightTrimAndTruncate()



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Created] (HADOOP-16831) Boundary condition to check if there is nothing to truncate in StringExpr functions

2020-01-27 Thread Ramesh Kumar Thangarajan (Jira)
Ramesh Kumar Thangarajan created HADOOP-16831:
-

 Summary: Boundary condition to check if there is nothing to 
truncate in StringExpr functions
 Key: HADOOP-16831
 URL: https://issues.apache.org/jira/browse/HADOOP-16831
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Ramesh Kumar Thangarajan


Add a boundary condition to check if there is nothing to truncate in StringExpr 
functions

truncate()

rightTrimAndTruncate()



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) LocalDirAllocator to provide diagnostics when file creation fails

2020-01-22 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Attachment: HADOOP-16769.7.patch
Status: Patch Available  (was: Open)

> LocalDirAllocator to provide diagnostics when file creation fails
> -
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: util
>Reporter: Ramesh Kumar Thangarajan
>Priority: Minor
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch, HADOOP-16769.6.patch, 
> HADOOP-16769.7.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) LocalDirAllocator to provide diagnostics when file creation fails

2020-01-22 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Status: Open  (was: Patch Available)

> LocalDirAllocator to provide diagnostics when file creation fails
> -
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: util
>Reporter: Ramesh Kumar Thangarajan
>Priority: Minor
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch, HADOOP-16769.6.patch, 
> HADOOP-16769.7.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) LocalDirAllocator to provide diagnostics when file creation fails

2020-01-21 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Attachment: HADOOP-16769.6.patch
Status: Patch Available  (was: Open)

> LocalDirAllocator to provide diagnostics when file creation fails
> -
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: util
>Reporter: Ramesh Kumar Thangarajan
>Priority: Minor
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch, HADOOP-16769.6.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) LocalDirAllocator to provide diagnostics when file creation fails

2020-01-21 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Status: Open  (was: Patch Available)

> LocalDirAllocator to provide diagnostics when file creation fails
> -
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: util
>Reporter: Ramesh Kumar Thangarajan
>Priority: Minor
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-19 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Attachment: HADOOP-16769.5.patch
Status: Patch Available  (was: Open)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch, HADOOP-16769.5.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-19 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Status: Open  (was: Patch Available)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-19 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Attachment: HADOOP-16769.4.patch
Status: Patch Available  (was: Open)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-19 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Attachment: (was: HADOOP-16769.4.patch)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-19 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Status: Open  (was: Patch Available)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-19 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Attachment: HADOOP-16769.4.patch
Status: Patch Available  (was: Open)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-19 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Status: Open  (was: Patch Available)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch, 
> HADOOP-16769.4.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-18 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Status: Open  (was: Patch Available)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-18 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Attachment: HADOOP-16769.3.patch
Status: Patch Available  (was: Open)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch, HADOOP-16769.3.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Commented] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-17 Thread Ramesh Kumar Thangarajan (Jira)


[ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998436#comment-16998436
 ] 

Ramesh Kumar Thangarajan commented on HADOOP-16769:
---

Hi [~gabor.bota], Please review the PR and let me know about your thoughts. 
Thanks!

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Updated] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-17 Thread Ramesh Kumar Thangarajan (Jira)


 [ 
https://issues.apache.org/jira/browse/HADOOP-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Kumar Thangarajan updated HADOOP-16769:
--
Attachment: HADOOP-16769.1.patch
Status: Patch Available  (was: Open)

> Log details of requested size and available capacity when file creation is 
> not successuful
> --
>
> Key: HADOOP-16769
> URL: https://issues.apache.org/jira/browse/HADOOP-16769
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: hdfs-client
>Reporter: Ramesh Kumar Thangarajan
>Priority: Major
> Attachments: HADOOP-16769.1.patch
>
>
> Log details of requested size and available capacity when file creation is 
> not successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org



[jira] [Created] (HADOOP-16769) Log details of requested size and available capacity when file creation is not successuful

2019-12-17 Thread Ramesh Kumar Thangarajan (Jira)
Ramesh Kumar Thangarajan created HADOOP-16769:
-

 Summary: Log details of requested size and available capacity when 
file creation is not successuful
 Key: HADOOP-16769
 URL: https://issues.apache.org/jira/browse/HADOOP-16769
 Project: Hadoop Common
  Issue Type: Improvement
  Components: hdfs-client
Reporter: Ramesh Kumar Thangarajan


Log details of requested size and available capacity when file creation is not 
successuful



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org