[
https://issues.apache.org/jira/browse/HDFS-13702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525528#comment-16525528
]
Sean Busbey commented on HDFS-13702:
------------------------------------
{quote}
Then, when it ran the hadoop-hdfs tests, they ran against the trunk snapshot
build rather than the patched snapshot build, and failed to compile. Sean's
going to file a YETUS JIRA about this and re-submit the patch build here.
{quote}
I wanna take a look at Hadoop's pom. ideally we shouldn't have the ASF snapshot
repo as a source of artifacts at all. I'm not sure there's a way for yetus to
proactively defend against it. (maybe use maven's {{--offline}} for build steps
after the one where we say we're downloading the world?)
> HTrace hooks taking 10-15% CPU in DFS client when disabled
> ----------------------------------------------------------
>
> Key: HDFS-13702
> URL: https://issues.apache.org/jira/browse/HDFS-13702
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: performance
> Affects Versions: 3.0.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Major
> Attachments: hdfs-13702.patch, hdfs-13702.patch, hdfs-13702.patch
>
>
> I am seeing DFSClient.newReaderTraceScope take ~15% CPU in a teravalidate
> workload even when HTrace is disabled. This is because it stringifies several
> integers. We should avoid all allocation and stringification when htrace is
> disabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
