You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Ari Rabkin (JIRA)" <ji...@apache.org> on 2009/01/15 09:30:00 UTC
[jira] Issue Comment Edited: (HADOOP-5038) remove
System.out.println statement
[ https://issues.apache.org/jira/browse/HADOOP-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664041#action_12664041 ]
asrabkin edited comment on HADOOP-5038 at 1/15/09 12:28 AM:
--------------------------------------------------------------
The goal is certainly a good one.
I have one hesitation though -- Given this patch, the HTTP response will never get read. I'm nervous that in a long-running connection, a buffer associated with the socket will fill up, and writes will block. Are you confident that won't happen? Do we have tests to cover long running large-data transfers, and in particular ones across the network?
was (Author: asrabkin):
Given this patch, the HTTP response will never get read. I'm nervous that in a long-running connection, a buffer associated with the socket will fill up, and writes will block. Are you confident that won't happen? Do we have tests to cover long running large-data transfers, and in particular ones across the network?
> remove System.out.println statement
> -----------------------------------
>
> Key: HADOOP-5038
> URL: https://issues.apache.org/jira/browse/HADOOP-5038
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/chukwa
> Reporter: Jerome Boulon
> Assignee: Jerome Boulon
> Attachments: HADOOP-5038.patch
>
>
> Starting the agent using the chuka-daemon.sh script redirect the standard output to a file. Only critical information should be outputted to stdout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.