[ https://issues.apache.org/jira/browse/HDFS-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855670#comment-16855670 ]
Ayush Saxena commented on HDFS-14542: ------------------------------------- If Quota by storage type is not set, then it just return without looping up, If we remove this check now, even if Quota by storage type is not set, it will Loop up for all storage types and then return, Instead of one check it will check equal to number of storage types. it saves one check, only if quota is set, which too is negligible and increases calls n times for if Quota is not set. I guess the present code is correct. > Remove redundant code when verify quota > --------------------------------------- > > Key: HDFS-14542 > URL: https://issues.apache.org/jira/browse/HDFS-14542 > Project: Hadoop HDFS > Issue Type: Improvement > Affects Versions: 3.1.1 > Reporter: Jinglun > Assignee: Jinglun > Priority: Minor > Attachments: HDFS-14542.patch > > > DirectoryWithQuotaFeature.verifyQuotaByStorageType() does the job of > verifying quota. It's redundant to call isQuotaByStorageTypeSet() because the > for each iterator nextline has done the same job. > {code:java} > private void verifyQuotaByStorageType(EnumCounters<StorageType> typeDelta) > throws QuotaByStorageTypeExceededException { > if (!isQuotaByStorageTypeSet()) { // REDUNDANT. > return; > } > for (StorageType t: StorageType.getTypesSupportingQuota()) { > if (!isQuotaByStorageTypeSet(t)) { // CHECK FOR EACH STORAGETYPE. > continue; > } > if (Quota.isViolated(quota.getTypeSpace(t), usage.getTypeSpace(t), > typeDelta.get(t))) { > throw new QuotaByStorageTypeExceededException( > quota.getTypeSpace(t), usage.getTypeSpace(t) + typeDelta.get(t), t); > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org