Accumulo-Pull-Requests - Build # 840 - Fixed

2017-05-25 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Accumulo-Pull-Requests (build #840)

Status: Fixed

Check console output at 
https://builds.apache.org/job/Accumulo-Pull-Requests/840/ to view the results.

[jira] [Commented] (ACCUMULO-4640) Accumulo shell is expecting instance.volumes in client.conf instead of accumulo-site.xml

2017-05-25 Thread Michael Miller (JIRA) 

[ 
https://issues.apache.org/jira/browse/ACCUMULO-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025247#comment-16025247
 ] 

Michael Miller commented on ACCUMULO-4640:
--

[~luigidifraia] does the shell work if you run it using the -z (or -zh and -zi) 
option? 

> Accumulo shell is expecting instance.volumes in client.conf instead of 
> accumulo-site.xml
> 
>
> Key: ACCUMULO-4640
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4640
> Project: Accumulo
>  Issue Type: Bug
>  Components: shell
>Affects Versions: 1.8.1
> Environment: [accumulo@master ~]$ cat /etc/redhat-release
> CentOS Linux release 7.3.1611 (Core)
> [accumulo@master ~]$ uname -a
> Linux master 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05 UTC 2017 
> x86_64 x86_64 x86_64 GNU/Linux
> [accumulo@master ~]$ java -version
> java version "1.8.0_112"
> Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)
> Hadoop: 2.8.0
> ZooKeeper: 3.4.10
> Accumulo: 1.8.1
>Reporter: Luigi Di Fraia
> Fix For: 1.8.2, 2.0.0
>
> Attachments: accumulo-env.sh, accumulo-site.xml
>
>
> Starting with Accumulo 1.8.1 we are getting the exception as per below when 
> the Accumulo shell is invoked:
> [accumulo@master ~]$ /usr/local/accumulo/bin/accumulo shell -u root -p 
> ***removed***
> 2017-05-18 14:31:23,667 [zookeeper.ZooUtil] ERROR: unable obtain instance id 
> at hdfs://master:9000/accumulo/instance_id
> 2017-05-18 14:31:23,669 [start.Main] ERROR: Thread 'shell' died.
> java.lang.RuntimeException: Accumulo not initialized, there is no instance id 
> at hdfs://master:9000/accumulo/instance_id
> at 
> org.apache.accumulo.core.zookeeper.ZooUtil.getInstanceIDFromHdfs(ZooUtil.java:66)
> at 
> org.apache.accumulo.core.zookeeper.ZooUtil.getInstanceIDFromHdfs(ZooUtil.java:51)
> at org.apache.accumulo.shell.Shell.getZooInstance(Shell.java:511)
> at org.apache.accumulo.shell.Shell.setInstance(Shell.java:473)
> at org.apache.accumulo.shell.Shell.config(Shell.java:322)
> at org.apache.accumulo.shell.Shell.execute(Shell.java:589)
> at org.apache.accumulo.start.Main$1.run(Main.java:120)
> at java.lang.Thread.run(Thread.java:745)
> The location used to look up the instance_id 
> (hdfs://master:9000/accumulo/instance_id) does not appear to be consistent 
> with this site configuration and I am not quite sure how it is being worked 
> out.
> The Accumulo Overview web page shows that the instance exists:
> Instance ID: 4264f11a-704f-4c1f-880f-08f6154232b2 
> Thu May 18 14:44:03 BST 2017
> The instance_id file is in Hadoop's HDFS:
> [accumulo@master ~]$ /usr/local/hadoop/bin/hdfs dfs -ls 
> /user/accumulo/accumulo/instance_id
> Found 1 items
> -rw-r--r--   3 accumulo supergroup  0 2017-05-18 14:27 
> /user/accumulo/accumulo/instance_id/4264f11a-704f-4c1f-880f-08f6154232b2
> Again, within the same environment as selected above apart for using Accumulo 
> 1.8.0, the shell can be invoked without issues.
> Here's a snippet from accumulo-site.xml:
>   
> instance.volumes
> hdfs://master:9000/user/accumulo/accumulo
> comma separated list of URIs for volumes. example: 
> hdfs://localhost:9000/accumulo
>   
> For historical reasons our "root volume" is not / but /user/accumulo although 
> the above stack trace suggests that / is being used as root volume.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ACCUMULO-4643) Allow iterators to interrupt themselves

2017-05-25 Thread Ivan Bella (JIRA) 
Ivan Bella created ACCUMULO-4643:


 Summary: Allow iterators to interrupt themselves
 Key: ACCUMULO-4643
 URL: https://issues.apache.org/jira/browse/ACCUMULO-4643
 Project: Accumulo
  Issue Type: Improvement
  Components: tserver
Affects Versions: 1.8.1, 2.0.0
Reporter: Ivan Bella
Assignee: Ivan Bella
 Fix For: 2.0.0


The idea here is to allow an iterator stack to send back a special key or throw 
a special exception which will allow the tablet server to tear down the scan to 
be rebuilt later.  This is to handle the case where an iterator is doing a lot 
of work without returning results to avoid starving out other scans.

There are two thoughts on how to do this:
1) A special "interrupt" key is returned from the getTopKey call that is 
detected in the Tablet.nextBatch call, is not added to the results, but is used 
to add an unfinished range and results in the remaining ranges to be deemed 
unfinished.
2) An special exception is thrown from the next or seek call that included the 
key of the current position, and the same actions are taken as in 1).




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)