[jira] [Commented] (ACCUMULO-4488) fix gaps in user manual section on Kerberos for clients

2016-10-07 Thread Sean Busbey (JIRA) 

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

Sean Busbey commented on ACCUMULO-4488:
---

I'm pretty sure anyone with builds.a.o access can make the needed changes or 
disable it. I'll make a go at the former and do the latter if needed.

Anyone know enough asciidoc to tell me how to correct the list issue?

> fix gaps in user manual section on Kerberos for clients 
> 
>
> Key: ACCUMULO-4488
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4488
> Project: Accumulo
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 1.7.1, 1.7.2
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 1.7.3, 1.8.1, 2.0.0
>
> Attachments: ACCUMULO-4488.1.patch, ACCUMULO-4488.2.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> clean up several gaps in the docs that I stumbled on while setting up a 
> cluster with kerberos for clients:
> * document setting up a superuser on an existing system that's enabling 
> kerberos
> * include example of verifying access for the superuser
> * per-user client configuration gives wrong filename
> * per-user client configuration required additions for kerberos missing 
> {{rpc.sasl.qop}}
> * document {{trace.token.property.keytab}}
> * note required permissions for trace user (Table.READ, Table.WRITE, 
> Table.ALTER_TABLE)



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

Accumulo-Master - Build # 1985 - Fixed

2016-10-07 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Accumulo-Master (build #1985)

Status: Fixed

Check console output at https://builds.apache.org/job/Accumulo-Master/1985/ to 
view the results.

[jira] [Updated] (ACCUMULO-4481) Remove property logger.dir.walog

2016-10-07 Thread Christopher Tubbs (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ACCUMULO-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher Tubbs updated ACCUMULO-4481:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Merged, but left {{release_notes}} label for updating release notes on next 
release.

> Remove property logger.dir.walog
> 
>
> Key: ACCUMULO-4481
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4481
> Project: Accumulo
>  Issue Type: Task
>Affects Versions: 1.8.0
>Reporter: Christopher Tubbs
>Assignee: Christopher Tubbs
>Priority: Minor
>  Labels: release_notes
> Fix For: 1.8.1, 2.0.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The old {{logger.dir.walog}} property no longer serves any purpose. It should 
> be removed. Upgrades aren't possible from 1.5 or earlier to 1.8 or later. 
> This property is only used to upgrade from 1.4 or earlier. Since that's no 
> longer possible, it should just be removed.
> Documentation and example accumulo-site.xml files should be updated.



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

[jira] [Reopened] (ACCUMULO-4488) fix gaps in user manual section on Kerberos for clients

2016-10-07 Thread Christopher Tubbs (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ACCUMULO-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher Tubbs reopened ACCUMULO-4488:
-

Reopening because the patch causes a generation bug. The item list in the 
"Administrative User" section of the kerberos chapter is broken. Line 273 
starts a new item list, instead of the intended addition of a third item. This 
appears to be caused by the injection of a block level element inside a list.

> fix gaps in user manual section on Kerberos for clients 
> 
>
> Key: ACCUMULO-4488
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4488
> Project: Accumulo
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 1.7.1, 1.7.2
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 1.7.3, 1.8.1, 2.0.0
>
> Attachments: ACCUMULO-4488.1.patch, ACCUMULO-4488.2.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> clean up several gaps in the docs that I stumbled on while setting up a 
> cluster with kerberos for clients:
> * document setting up a superuser on an existing system that's enabling 
> kerberos
> * include example of verifying access for the superuser
> * per-user client configuration gives wrong filename
> * per-user client configuration required additions for kerberos missing 
> {{rpc.sasl.qop}}
> * document {{trace.token.property.keytab}}
> * note required permissions for trace user (Table.READ, Table.WRITE, 
> Table.ALTER_TABLE)



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

[jira] [Commented] (ACCUMULO-4493) Shell should be able to use keytab login

2016-10-07 Thread Christopher Tubbs (JIRA) 

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

Christopher Tubbs commented on ACCUMULO-4493:
-

Do you know if it's possible to renew outside the shell process to get things 
going again for a long-running shell?

> Shell should be able to use keytab login
> 
>
> Key: ACCUMULO-4493
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4493
> Project: Accumulo
>  Issue Type: New Feature
>  Components: shell
>Reporter: Sean Busbey
>Priority: Minor
> Fix For: 2.0.0
>
>
> Users should be able to launch the shell in a kerberos deployment using a 
> keytab.
> current workaround: use the system shell to kinit with the keytab, then 
> launch the shell, then kdestroy
> Workaround doesn't allow re-login from keytab for long running shell.



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

[jira] [Commented] (ACCUMULO-4492) operations tool to migrate existing users when enabling Kerberos

2016-10-07 Thread Christopher Tubbs (JIRA) 

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

Christopher Tubbs commented on ACCUMULO-4492:
-

It sounds like you're suggesting something like what idmapd does, but as a 
one-time use, instead of as a persistent mapping service.

> operations tool to migrate existing users when enabling Kerberos
> 
>
> Key: ACCUMULO-4492
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4492
> Project: Accumulo
>  Issue Type: New Feature
>Reporter: Sean Busbey
> Fix For: 2.0.0
>
>
> When converting an existing cluster to use Kerberos, existing user 
> permissions aren't much use unless the user names happen to be formatted like 
> Kerberos principals.
> An offline tool that folks migrating can use to map existing user names to 
> principals would be super useful.
> Essentially something like:
> {code}
> $ accumulo kerberos-migration --include-users=* --exclude-users=root 
> --no-instance --realm=EXAMPLE.COM
> Migrating users matching '*' and not matching 'root'.
> User principals will not have an instance component.
> User principals will be in the realm 'EXAMPLE.COM'
> Found user 'auser', converted to 'au...@example.com'
> Found user 'another_user', converted to 'another_u...@example.com'
> Found user 'hpnewton', converted to 'hpnew...@example.com'
> Found user 'root', skipped due to exclusion rule
> {code}



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

[jira] [Updated] (ACCUMULO-4490) Simplify Accumulo scripts and config files

2016-10-07 Thread Christopher Tubbs (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ACCUMULO-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher Tubbs updated ACCUMULO-4490:

Affects Version/s: (was: 2.0.0)

> Simplify Accumulo scripts and config files
> --
>
> Key: ACCUMULO-4490
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4490
> Project: Accumulo
>  Issue Type: Improvement
>  Components: scripts, start
>Reporter: Mike Walch
>Assignee: Mike Walch
> Fix For: 2.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, there are too many Accumulo scripts and config files in 'bin' and 
> 'conf' respectively.  It is confusing to know which scripts or configuration 
> file should be used.  Some scripts are just used by other scripts.  Some 
> configuration file are only needed in rare situations.  Scripts also lack 
> usage/help docs.
> Below is general plan to fix this:
> # Reduce the number of scripts in 'bin' directory
> #* Move implementation/uncommon scripts to 'scripts' directory
> #* Scripts in `bin` should be simple wrapper scripts that either call Java or 
> implementation script in `scripts' directory
> # Scripts in 'bin' should have good help/usage information.
> # Only generate one set of example configuration in 'conf/examples'. User can 
> use bootstrap-config to generate config for different environments.
> # Change bootstrap-config to only generate minimal config necessary.
> # For uncommon configuration files (like logging), fall back to example file 
> in 'conf/examples' if file not present in 'conf'



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

[jira] [Commented] (ACCUMULO-2180) provide an interface for FB Presto

2016-10-07 Thread Josh Elser (JIRA) 

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

Josh Elser commented on ACCUMULO-2180:
--

Cool, thanks for the info, [~electrum]. We could/should get this posted on our 
website. Maybe you or [~adamjshook] would be interested in that? 
https://github.com/apache/accumulo/tree/gh-pages

> provide an interface for FB Presto
> --
>
> Key: ACCUMULO-2180
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2180
> Project: Accumulo
>  Issue Type: New Feature
>Reporter: Arshak Navruzyan
>Priority: Trivial
>
> Presto (http://prestodb.io/) appears to be gaining support as a faster 
> alternative to Hive.  
> Presto can query different data stores using connectors that provide 
> interfaces for fetching metadata, getting data locations, and accessing the 
> data itself.   Currently Presto ships with a HD1, HD2 hive connectors. FB has 
> a prototype connector for Hbase that they plan to open source at some point.  
> There is also a connector for Cassandra 
> (https://github.com/MartinWeindel/presto/blob/master/presto-cassandra/README.md)



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

Accumulo-Master - Build # 1984 - Failure

2016-10-07 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Accumulo-Master (build #1984)

Status: Failure

Check console output at https://builds.apache.org/job/Accumulo-Master/1984/ to 
view the results.

[jira] [Resolved] (ACCUMULO-4453) Remove debug log spam from ScanDataSource

2016-10-07 Thread Josh Elser (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ACCUMULO-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Elser resolved ACCUMULO-4453.
--
Resolution: Fixed

Thanks again for the review, Marc!

> Remove debug log spam from ScanDataSource
> -
>
> Key: ACCUMULO-4453
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4453
> Project: Accumulo
>  Issue Type: Sub-task
>  Components: tserver
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Minor
> Fix For: 2.0.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> I happened to be looking at a TabletServer log file for an ExampleIT method 
> and just saw tons of 
> {noformat}
> 2016-09-09 17:18:08,617 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,625 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,630 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,635 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,640 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,645 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,651 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,657 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,662 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,667 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,673 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,677 [tablet.ScanDataSource] DEBUG: new scan data source, 
> tablet: org.apache.accumulo.tserver.tablet.Tablet@58eb5149, options: [auths=, 
> batchTimeOut=9223372036854775807, context=null, columns=[], 
> interruptFlag=false, isolated=false, num=1000, samplerConfig=null], 
> interruptFlag: false, loadIterators: true
> 2016-09-09 17:18:08,682 [tablet.ScanDataSource] DEBUG: new scan data

[jira] [Commented] (ACCUMULO-4488) fix gaps in user manual section on Kerberos for clients

2016-10-07 Thread Josh Elser (JIRA) 

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

Josh Elser commented on ACCUMULO-4488:
--

Catching up: this looks great! Thanks for making these additions!

bq. Unrelated, can we disable Yetus until we get it fixed?

I don't know of a way to do this. It would require an infra ask. Do you have 
cycles to get Yetus running again? :)

> fix gaps in user manual section on Kerberos for clients 
> 
>
> Key: ACCUMULO-4488
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4488
> Project: Accumulo
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 1.7.1, 1.7.2
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 1.7.3, 1.8.1, 2.0.0
>
> Attachments: ACCUMULO-4488.1.patch, ACCUMULO-4488.2.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> clean up several gaps in the docs that I stumbled on while setting up a 
> cluster with kerberos for clients:
> * document setting up a superuser on an existing system that's enabling 
> kerberos
> * include example of verifying access for the superuser
> * per-user client configuration gives wrong filename
> * per-user client configuration required additions for kerberos missing 
> {{rpc.sasl.qop}}
> * document {{trace.token.property.keytab}}
> * note required permissions for trace user (Table.READ, Table.WRITE, 
> Table.ALTER_TABLE)



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

[jira] [Resolved] (ACCUMULO-3336) ZK session reconnect still results in loss of ZK lock

2016-10-07 Thread Josh Elser (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ACCUMULO-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Elser resolved ACCUMULO-3336.
--
   Resolution: Cannot Reproduce
Fix Version/s: (was: 1.8.1)

This issue is getting far too much traction from users who think that this is a 
bug.

The issue I reported here is not a simple SESSION_EXPIRED from ZooKeeper. 
Unless you really understand what's going on, you need to tune the 
configuration of Accumulo, HDFS or the Operation System. This is not a "bug".

> ZK session reconnect still results in loss of ZK lock
> -
>
> Key: ACCUMULO-3336
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3336
> Project: Accumulo
>  Issue Type: Bug
>  Components: zookeeper
>Affects Versions: 1.5.2, 1.6.1
>Reporter: Josh Elser
>
> Saw the following
> {noformat}
> 2014-11-14 08:38:30,612 [zookeeper.DistributedWorkQueue] INFO : Got 
> unexpected zookeeper event: None for 
> /accumulo/00f38e67-3c29-4cf0-a394-f423a0b33b6b/bulk_failed_copyq
> 2014-11-14 08:38:30,621 [zookeeper.ZooCache] WARN : Saw (possibly) transient 
> exception communicating with ZooKeeper, will retry
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for 
> /accumulo/00f38e67-3c29-4cf0-a394-f423a0b33b6b/config/tserver.compaction.warn.time
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
>   at org.apache.accumulo.fate.zookeeper.ZooCache$2.run(ZooCache.java:260)
>   at org.apache.accumulo.fate.zookeeper.ZooCache.retry(ZooCache.java:157)
>   at org.apache.accumulo.fate.zookeeper.ZooCache.get(ZooCache.java:285)
>   at org.apache.accumulo.fate.zookeeper.ZooCache.get(ZooCache.java:232)
>   at 
> org.apache.accumulo.server.conf.ZooConfiguration.get(ZooConfiguration.java:96)
>   at 
> org.apache.accumulo.server.conf.ZooConfiguration._get(ZooConfiguration.java:65)
>   at 
> org.apache.accumulo.server.conf.ZooConfiguration.get(ZooConfiguration.java:90)
>   at 
> org.apache.accumulo.core.conf.AccumuloConfiguration.getTimeInMillis(AccumuloConfiguration.java:136)
>   at 
> org.apache.accumulo.tserver.CompactionWatcher.run(CompactionWatcher.java:84)
>   at 
> org.apache.accumulo.server.util.time.SimpleTimer$LoggingTimerTask.run(SimpleTimer.java:42)
>   at java.util.TimerThread.mainLoop(Timer.java:555)
>   at java.util.TimerThread.run(Timer.java:505)
> 2014-11-14 08:38:30,672 [zookeeper.DistributedWorkQueue] INFO : Got 
> unexpected zookeeper event: None for 
> /accumulo/00f38e67-3c29-4cf0-a394-f423a0b33b6b/recovery
> 2014-11-14 08:38:30,672 [zookeeper.ZooLock] DEBUG: event null None 
> Disconnected
> 2014-11-14 08:38:31,484 [zookeeper.ZooReader] WARN : Saw (possibly) transient 
> exception communicating with ZooKeeper
> org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode 
> = Session expired for 
> /accumulo/00f38e67-3c29-4cf0-a394-f423a0b33b6b/tservers/ip-172-31-13-177:37709
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:127)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
>   at 
> org.apache.accumulo.fate.zookeeper.ZooReader.getStatus(ZooReader.java:109)
>   at org.apache.accumulo.fate.zookeeper.ZooLock.process(ZooLock.java:381)
>   at 
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:522)
>   at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498)
> 2014-11-14 08:38:31,484 [zookeeper.ZooCache] WARN : Saw (possibly) transient 
> exception communicating with ZooKeeper, will retry
> org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode 
> = Session expired for 
> /accumulo/00f38e67-3c29-4cf0-a394-f423a0b33b6b/tables/!0/namespace
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:127)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
>   at org.apache.accumulo.fate.zookeeper.ZooCache$2.run(ZooCache.java:260)
>   at org.apache.accumulo.fate.zookeeper.ZooCache.retry(ZooCache.java:157)
>   at org.apache.accumulo.fate.zookeeper.ZooCache.get(ZooCache.java:285)
>   at org.apache.accumulo.fate.zookeeper.ZooCache.get(ZooCache.java:232)
>   at 
> org.apache.accumulo.core.client.impl.Tables.getNamespaceId(Tables.java:304)
>   at 
> org.apache.accumulo.server.conf.TableParentConfiguration.getNamespaceId(TableParentConfiguration.java:47)
>   at 
>

[jira] [Updated] (ACCUMULO-4488) fix gaps in user manual section on Kerberos for clients

2016-10-07 Thread Sean Busbey (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ACCUMULO-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated ACCUMULO-4488:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

pushed changes and updated user manual on website.

> fix gaps in user manual section on Kerberos for clients 
> 
>
> Key: ACCUMULO-4488
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4488
> Project: Accumulo
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 1.7.1, 1.7.2
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 1.7.3, 1.8.1, 2.0.0
>
> Attachments: ACCUMULO-4488.1.patch, ACCUMULO-4488.2.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> clean up several gaps in the docs that I stumbled on while setting up a 
> cluster with kerberos for clients:
> * document setting up a superuser on an existing system that's enabling 
> kerberos
> * include example of verifying access for the superuser
> * per-user client configuration gives wrong filename
> * per-user client configuration required additions for kerberos missing 
> {{rpc.sasl.qop}}
> * document {{trace.token.property.keytab}}
> * note required permissions for trace user (Table.READ, Table.WRITE, 
> Table.ALTER_TABLE)



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