[ https://issues.apache.org/jira/browse/HDFS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HDFS-475:
----------------------------------------
Affects Version/s: 0.21.0
Hadoop Flags: [Reviewed]
Also tried
{noformat}
ant run-test-hdfs-fault-inject -Dtestcase=TestFiDataTransferProtocol
{noformat}
with the patch posted in HDFS-483. It works.
Note that the patch changes the ant target name as shown below.
{noformat}
- <target name="injectfaults" depends="compile" description="Weaves aspects into precomplied
HDFS classes">
+ <target name="compile-fault-inject" depends="compile-core, compile-hdfs-test">
{noformat}
"injectfaults" was introduced by HDFS-436 which is committed to 0.21. I think this is not
an incompatible change since 0.21 is not yet released.
> Create a separate targets for fault injection related test and jar files creation files
> ---------------------------------------------------------------------------------------
>
> Key: HDFS-475
> URL: https://issues.apache.org/jira/browse/HDFS-475
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: build
> Affects Versions: 0.21.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Fix For: 0.21.0
>
> Attachments: HDFS-475.patch, HDFS-475.patch, HDFS-475.patch, HDFS-475.patch,
HDFS-475.patch
>
>
> Current implementation of the FI framework allows to mix faults into production classes,
e.g. into build/ folder.
> Although the default probability level is set to zero it doesn't look clean and might
potentially over complicate the build and release process.
> FI related targets are better be logically and physically separated, e.g. to put instrumented
artifacts into a separate folder, say, build-fi/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|