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 "Hudson (JIRA)" <ji...@apache.org> on 2008/08/22 14:34:51 UTC
[jira] Commented: (HADOOP-3863) Use a thread-local rather than
static ENCODER/DECODER variables in Text for synchronization
[ https://issues.apache.org/jira/browse/HADOOP-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624749#action_12624749 ]
Hudson commented on HADOOP-3863:
--------------------------------
Integrated in Hadoop-trunk #581 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])
> Use a thread-local rather than static ENCODER/DECODER variables in Text for synchronization
> -------------------------------------------------------------------------------------------
>
> Key: HADOOP-3863
> URL: https://issues.apache.org/jira/browse/HADOOP-3863
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Priority: Critical
> Fix For: 0.19.0
>
> Attachments: HADOOP-3863_0_20080730.patch, HADOOP-3863_1_20080730.patch
>
>
> Text.{ENCODER|DECODER} are static variables which need to be synchronized in Text.{read|write}String; given that lots of RPC code calls Text.{read|write}String the contention for this lock shows up very significantly on large clusters.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.