[jira] [Created] (ACCUMULO-3766) Bulk ingest fails on volume configuration mismatch

["Josh Elser (JIRA)" <ji...@apache.org>]

Josh Elser created ACCUMULO-3766:
------------------------------------

             Summary: Bulk ingest fails on volume configuration mismatch
                 Key: ACCUMULO-3766
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3766
             Project: Accumulo
          Issue Type: Bug
          Components: client
            Reporter: Josh Elser
            Priority: Blocker
             Fix For: 1.7.0


Saw this running the Bulk randomwalk module

{code}
error preparing the bulk import directory
	java.io.IOException: hdfs://jelser-accumulo-6.novalocal:8020/tmp/bulk_15333dff-747b-47e2-ae23-781da54da3f4 is not in a volume configured for Accumulo
		at org.apache.accumulo.master.tableOps.BulkImport.createNewBulkDir(BulkImport.java:149)
		at org.apache.accumulo.master.tableOps.BulkImport.prepareBulkImport(BulkImport.java:178)
		at org.apache.accumulo.master.tableOps.BulkImport.call(BulkImport.java:136)
		at org.apache.accumulo.master.tableOps.BulkImport.call(BulkImport.java:70)
		at org.apache.accumulo.master.tableOps.TraceRepo.call(TraceRepo.java:57)
		at org.apache.accumulo.fate.Fate$TransactionRunner.run(Fate.java:73)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
		at org.apache.accumulo.fate.util.LoggingRunnable.run(LoggingRunnable.java:35)
		at java.lang.Thread.run(Thread.java:745)
{code}

accumulo-site.xml has

{code}
  <property>
    <name>instance.volumes</name>
    <value>hdfs://jelser-accumulo-6:8020/user/accumulo/data</value>
    <description>comma separated list of URIs for volumes. example: hdfs://localhost:9000/accumulo</description>
  </property>
{code}

My hunch is that I had issues because I put in the shortname instead of the FQDN in instance.volumes.

Some thoughts:

1. Can we make this error detection smarter?
2. Do we have this issue documented (where multiple names can refer to the same namenode)?

Marked as blocker against 1.7.0 to get visibility and discussion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)