You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by ct...@apache.org on 2016/08/17 00:18:32 UTC

[04/10] accumulo git commit: ACCUMULO-4315 Remove confusing log message

ACCUMULO-4315 Remove confusing log message

Remove an unnecessarily confusing log message, about using a volume
which is not contained in instance.volumes. There's no reason to warn
about this, because it's not a problem. Further, it is expected in some
cases, such as bulk import, when files are imported from outside an
Accumulo "Volume".


Project: http://git-wip-us.apache.org/repos/asf/accumulo/repo
Commit: http://git-wip-us.apache.org/repos/asf/accumulo/commit/7efbbd5d
Tree: http://git-wip-us.apache.org/repos/asf/accumulo/tree/7efbbd5d
Diff: http://git-wip-us.apache.org/repos/asf/accumulo/diff/7efbbd5d

Branch: refs/heads/master
Commit: 7efbbd5dd762debaba39b1cdaa6011a06b5d299a
Parents: 02ac592
Author: Christopher Tubbs <ct...@apache.org>
Authored: Tue Aug 16 20:12:24 2016 -0400
Committer: Christopher Tubbs <ct...@apache.org>
Committed: Tue Aug 16 20:12:24 2016 -0400

----------------------------------------------------------------------
 .../java/org/apache/accumulo/server/fs/VolumeManagerImpl.java  | 6 ------
 1 file changed, 6 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/accumulo/blob/7efbbd5d/server/base/src/main/java/org/apache/accumulo/server/fs/VolumeManagerImpl.java
----------------------------------------------------------------------
diff --git a/server/base/src/main/java/org/apache/accumulo/server/fs/VolumeManagerImpl.java b/server/base/src/main/java/org/apache/accumulo/server/fs/VolumeManagerImpl.java
index 70332da..756af43 100644
--- a/server/base/src/main/java/org/apache/accumulo/server/fs/VolumeManagerImpl.java
+++ b/server/base/src/main/java/org/apache/accumulo/server/fs/VolumeManagerImpl.java
@@ -308,12 +308,6 @@ public class VolumeManagerImpl implements VolumeManager {
               return candidateVolume;
             }
           }
-
-          // For the same reason as we can have multiple Volumes within a single filesystem
-          // we could also not find a matching one. We should still provide a Volume with the
-          // correct FileSystem even though we don't know what the proper base dir is
-          // e.g. Files on volumes that are now removed
-          log.debug("Found candidate Volumes for Path but none of the Volumes are valid for the candidates: " + path);
         } else {
           log.debug("Could not determine volume for Path: " + path);
         }