date:20150202

[jira] [Commented] (HADOOP-11518) Prefix-based per-RPC server configuration

2015-02-02 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-11518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302034#comment-14302034
 ] 

Hadoop QA commented on HADOOP-11518:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12695968/HADOOP-11518.v2.patch
  against trunk revision 3472e3b.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/5557//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/5557//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/5557//console

This message is automatically generated.

 Prefix-based per-RPC server configuration
 -

 Key: HADOOP-11518
 URL: https://issues.apache.org/jira/browse/HADOOP-11518
 Project: Hadoop Common
  Issue Type: Improvement
  Components: ipc
Reporter: Kihwal Lee
Assignee: Kihwal Lee
 Attachments: HADOOP-11518.patch, HADOOP-11518.v2.patch


 If a process runs multiple RPC servers, there is no way to individually set 
 their IPC parameters beyond what's supported by the RPC Builder.  If a 
 configuration is shared among many nodes, this is more problematic. 
 In this jira, a prefix-based per-server configuration is proposed.  When an 
 RPC server is built, a prefix can be specified, which will then be prepended 
 to keys when retrieving configured values.  There will be an option to 
 fall-back to using the key without the prefix when no value is found with the 
 prefix, thus making this feature compatible with the current way of 
 configuring servers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (HADOOP-10948) SwiftNativeFileSystem's directory is incompatible with Swift and Horizon

2015-02-02 Thread David Dobbins (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-10948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302051#comment-14302051
]

David Dobbins commented on HADOOP-10948:

Is there an avenue for maintaining backwards compatibility? It seems the only
risk is for directories already created in swift with SwiftNativeFileSystem.
Would it suffice to only create new directories using the trailing-slash model
but to recognize either model for the purposes of reading existing directories?

SwiftNativeFileSystem's directory is incompatible with Swift and Horizon

Key: HADOOP-10948
URL: https://issues.apache.org/jira/browse/HADOOP-10948
Project: Hadoop Common
Issue Type: Bug
Components: fs/swift
Affects Versions: 3.0.0
Reporter: Kazuki OIKAWA
Assignee: Kazuki OIKAWA
Attachments: HADOOP-10948-2.patch, HADOOP-10948.patch

SwiftNativeFileSystem's directory representation is zero-byte file.
But in Swift / Horizon, directory representation is a trailing-slash.
This incompatibility has the following issues.
* SwiftNativeFileSystem can't see pseudo-directory made by OpenStack Horizon
* Swift/Horizon can't see pseudo-directory made by SwiftNativeFileSystem. But
Swift/Horizon see a zero-byte file instead of that pseudo-directory.
* SwiftNativeFileSystem can't see a file if there is no intermediate
pseudo-directory object.
* SwiftNativeFileSystem makes two objects when making a single directory
(e.g. hadoop fs -mkdir swift://test.test/dir/ = dir and dir/ created)

60 matches

Mail list logo