[jira] Updated: (HADOOP-702) DFS Upgrade Proposal

[ http://issues.apache.org/jira/browse/HADOOP-702?page=all ] Konstantin Shvachko updated HADOOP-702: --- Attachment: DFSUpgradeProposal2.html I substantially modified the upgrade proposal. - There will be more changes in the data layout. Please let m

Re: Administrative Request

In gmail, I create two filters: mail Matches: to:(hadoop-dev@lucene.apache.org) subject:(-[jira]) will skip inbox and applied with label "hdp-dev" mail Matches: to:(hadoop-dev@lucene.apache.org) subject:([jira]) will skip inbox and applied with label "hdp-dev-jira" On 11/17/06, Doug Cutting <[EMA

[jira] Commented: (HADOOP-673) the task execution environment should have a current working directory that is task specific

[ http://issues.apache.org/jira/browse/HADOOP-673?page=comments#action_12450942 ] Owen O'Malley commented on HADOOP-673: -- Richard, I don't understand why having the jar expanded in ".." is unacceptable to you. It seems to me the requirement

Re: [jira] Commented: (HADOOP-673) the task execution environment should have a current working directory that is task specific

+1 on Richard's comments +1 on Dick's (MR should symlink the files that belong to the task into the task running directory) -10 on ../work On Nov 17, 2006, at 4:25 PM, Richard Kasperski (JIRA) wrote: [ http://issues.apache.org/jira/browse/HADOOP-673? page=comments#action_12450936 ]

[jira] Updated: (HADOOP-677) RPC should send a fixed header and version at the start of connection

[ http://issues.apache.org/jira/browse/HADOOP-677?page=all ] Owen O'Malley updated HADOOP-677: - Status: Patch Available (was: Open) > RPC should send a fixed header and version at the start of connection > ---

[jira] Updated: (HADOOP-677) RPC should send a fixed header and version at the start of connection

[ http://issues.apache.org/jira/browse/HADOOP-677?page=all ] Owen O'Malley updated HADOOP-677: - Attachment: rpc-header.patch This patch causes the server to ignore a header on the start of ipc/rpc connections that look like: "hrpc" The client has a s

[jira] Commented: (HADOOP-673) the task execution environment should have a current working directory that is task specific

[ http://issues.apache.org/jira/browse/HADOOP-673?page=comments#action_12450936 ] Richard Kasperski commented on HADOOP-673: -- I think that it is very important that there be a way for an application to run in a sandbox /jobcache// that

[jira] Updated: (HADOOP-709) streaming job with Control characters in the command causes runtime exception in the job tracker

[ http://issues.apache.org/jira/browse/HADOOP-709?page=all ] dhruba borthakur updated HADOOP-709: Status: Patch Available (was: Open) URLEncode the streaming related key-value pairs in the job.xml file. stream.map.streamprocessor stream.reduce

[jira] Updated: (HADOOP-709) streaming job with Control characters in the command causes runtime exception in the job tracker

[ http://issues.apache.org/jira/browse/HADOOP-709?page=all ] dhruba borthakur updated HADOOP-709: Attachment: ctrlchars_in_streaming URLEncode the streaming related key-value pairs in the job.xml file. stream.map.streamprocessor stream.reduce.s

[jira] Assigned: (HADOOP-673) the task execution environment should have a current working directory that is task specific

[ http://issues.apache.org/jira/browse/HADOOP-673?page=all ] Mahadev konar reassigned HADOOP-673: Assignee: Mahadev konar (was: Owen O'Malley) > the task execution environment should have a current working directory that > is task specific > --

[jira] Commented: (HADOOP-673) the task execution environment should have a current working directory that is task specific

[ http://issues.apache.org/jira/browse/HADOOP-673?page=comments#action_12450931 ] Mahadev konar commented on HADOOP-673: -- I have the following proposal: The tasks run in the task specific directory that is /jobcache// to create a virtual i

[jira] Created: (HADOOP-735) The underlying data structure, ByteArrayOutputStream, for buffer type of Jute record is inappropriate

The underlying data structure, ByteArrayOutputStream, for buffer type of Jute record is inappropriate -- Key: HADOOP-735 URL: http://issues.apache.org/jira/browse

[jira] Updated: (HADOOP-734) Link to the FAQ in the "Documentation" section of the hadoop website

[ http://issues.apache.org/jira/browse/HADOOP-734?page=all ] Konstantin Shvachko updated HADOOP-734: --- Status: Patch Available (was: Open) Fix Version/s: 0.9.0 Affects Version/s: 0.8.0 > Link to the FAQ in the "Documentation"

[jira] Updated: (HADOOP-734) Link to the FAQ in the "Documentation" section of the hadoop website

[ http://issues.apache.org/jira/browse/HADOOP-734?page=all ] Konstantin Shvachko updated HADOOP-734: --- Attachment: FAQLink.patch The patch contains both modified site.xml and a diff of files generated by forrest. > Link to the FAQ in the "Documen

[jira] Created: (HADOOP-734) Link to the FAQ in the "Documentation" section of the hadoop website

Link to the FAQ in the "Documentation" section of the hadoop website Key: HADOOP-734 URL: http://issues.apache.org/jira/browse/HADOOP-734 Project: Hadoop Issue Type: Bug

[jira] Updated: (HADOOP-692) Rack-aware Replica Placement

[ http://issues.apache.org/jira/browse/HADOOP-692?page=all ] Hairong Kuang updated HADOOP-692: - Attachment: Rack_aware_HDFS_proposal.pdf Attached please read my revised proposal. > Rack-aware Replica Placement > > >

[jira] Commented: (HADOOP-733) dfs shell has inconsistent exit codes

[ http://issues.apache.org/jira/browse/HADOOP-733?page=comments#action_12450876 ] Christian Kunz commented on HADOOP-733: --- I applied the patch. Thank you, Dhruba, for the quick response. > dfs shell has inconsistent exit codes > --

[jira] Commented: (HADOOP-707) Final map task gets stuck

[ http://issues.apache.org/jira/browse/HADOOP-707?page=comments#action_12450855 ] Owen O'Malley commented on HADOOP-707: -- Where is the task being lost? Use the web/ui to see if the JobTracker thinks the map is running somewhere. If so, foll

[jira] Updated: (HADOOP-733) dfs shell has inconsistent exit codes

[ http://issues.apache.org/jira/browse/HADOOP-733?page=all ] dhruba borthakur updated HADOOP-733: Status: Patch Available (was: Open) This patch contains a fix to return appropriate error codes while trying to delete or cat a non-existent file. It

[jira] Updated: (HADOOP-733) dfs shell has inconsistent exit codes

[ http://issues.apache.org/jira/browse/HADOOP-733?page=all ] dhruba borthakur updated HADOOP-733: Attachment: shellerrorcodes.patch This patch contains a fix to return appropriate error codes while trying to delete or cat a non-existent file. It als

[jira] Assigned: (HADOOP-733) dfs shell has inconsistent exit codes

[ http://issues.apache.org/jira/browse/HADOOP-733?page=all ] dhruba borthakur reassigned HADOOP-733: --- Assignee: dhruba borthakur > dfs shell has inconsistent exit codes > - > > Key: HADOOP-733 >

[jira] Commented: (HADOOP-707) Final map task gets stuck

[ http://issues.apache.org/jira/browse/HADOOP-707?page=comments#action_12450802 ] Johan Oskarson commented on HADOOP-707: --- Same problem, different job. Full thread dump. 2006-11-17 15:08:14,707 INFO org.apache.hadoop.mapred.TaskTracker: t

[jira] Created: (HADOOP-733) dfs shell has inconsistent exit codes

dfs shell has inconsistent exit codes - Key: HADOOP-733 URL: http://issues.apache.org/jira/browse/HADOOP-733 Project: Hadoop Issue Type: Bug Components: dfs Affects Versions: 0.8.0