[
https://issues.apache.org/jira/browse/HDFS-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644880#comment-13644880
]
Suresh Srinivas commented on HDFS-4489:
---------------------------------------
Here is NNBench for delete operations (run with 100 threads simultaneously
running:
||Opertaions||Elapsed||OpsPerSec||AvgTim||
|100000|19243|5196.694902|19|
|100000|18598|5376.92225|18|
|100000|17819|5611.987205|17|
|100000|17953|5570.099705|17|
|100000|18077|5531.891354|18|
|100000|17948|5571.651437|17|
|100000|18080|5530.973451|18|
|100000|18032|5545.696539|18|
|100000|18431|5425.641582|18|
|100000|17735|5638.567804|17|
|100000|1819|.6 5500|012623 17.7|
||Opertaions||Elapsed||OpsPerSec||AvgTim||
|100000|18029|5546.619336|17|
|100000|18527|5397.527932|18|
|100000|18164|5505.395287|18|
|100000|18486|5409.49908|18|
|100000|18053|5539.245555|18|
|100000|18313|5460.601758|18|
|100000|18299|5464.779496|18|
|100000|17878|5593.466831|17|
|100000|18178|5501.155243|18|
|100000|18084|5529.750055|18|
|100000|1820|.1 5494|804057 17.8|
> Use InodeID as as an identifier of a file in HDFS protocols and APIs
> --------------------------------------------------------------------
>
> Key: HDFS-4489
> URL: https://issues.apache.org/jira/browse/HDFS-4489
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Brandon Li
> Assignee: Brandon Li
> Fix For: 2.0.5-beta
>
> Attachments: 4434.optimized.patch
>
>
> The benefit of using InodeID to uniquely identify a file can be multiple
> folds. Here are a few of them:
> 1. uniquely identify a file cross rename, related JIRAs include HDFS-4258,
> HDFS-4437.
> 2. modification checks in tools like distcp. Since a file could have been
> replaced or renamed to, the file name and size combination is no t reliable,
> but the combination of file id and size is unique.
> 3. id based protocol support (e.g., NFS)
> 4. to make the pluggable block placement policy use fileid instead of
> filename (HDFS-385).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
