[jira] [Resolved] (ATLAS-67) Validate with secure zookeeper server for titan interaction with hbase and solr
[ https://issues.apache.org/jira/browse/ATLAS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron resolved ATLAS-67. - Resolution: Fixed Commit: 2ed767c21cde5de256b914655d16e2dd4b15ab6a [2ed767c] Parents: 113feb3af4 Author: Jon Maron jma...@hortonworks.com Date: August 26, 2015 at 3:36:46 PM EDT Labels: HEAD origin/master origin/HEAD master ATLAS-67 add zk service principal for secure tests Validate with secure zookeeper server for titan interaction with hbase and solr --- Key: ATLAS-67 URL: https://issues.apache.org/jira/browse/ATLAS-67 Project: Atlas Issue Type: Task Reporter: Suma Shivaprasad Assignee: Jonathan Maron Attachments: org.apache.atlas.hive.hook.NegativeSSLAndKerberosHiveHookIT.txt -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-115) Remove unnecessary log4j.xml in typesystem
[ https://issues.apache.org/jira/browse/ATLAS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715425#comment-14715425 ] Jonathan Maron commented on ATLAS-115: -- Downloaded patch and tested locally (mvn clean verify). Will go ahead and commit the fix. Remove unnecessary log4j.xml in typesystem -- Key: ATLAS-115 URL: https://issues.apache.org/jira/browse/ATLAS-115 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Suma Shivaprasad Assignee: Suma Shivaprasad Fix For: 0.6-incubating Attachments: ATLAS-115.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-67) Validate with secure zookeeper server for titan interaction with hbase and solr
[ https://issues.apache.org/jira/browse/ATLAS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713424#comment-14713424 ] Jonathan Maron commented on ATLAS-67: - Were you able to download and test from review board? Validate with secure zookeeper server for titan interaction with hbase and solr --- Key: ATLAS-67 URL: https://issues.apache.org/jira/browse/ATLAS-67 Project: Atlas Issue Type: Task Reporter: Suma Shivaprasad Assignee: Jonathan Maron Attachments: org.apache.atlas.hive.hook.NegativeSSLAndKerberosHiveHookIT.txt -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-67) Validate with secure zookeeper server for titan interaction with hbase and solr
[ https://issues.apache.org/jira/browse/ATLAS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713665#comment-14713665 ] Jonathan Maron commented on ATLAS-67: - Do you feel changing the default port for zookeeper in the distributed profile is appropriate? It would certainly support local testing, but is not the common port for ZK. Validate with secure zookeeper server for titan interaction with hbase and solr --- Key: ATLAS-67 URL: https://issues.apache.org/jira/browse/ATLAS-67 Project: Atlas Issue Type: Task Reporter: Suma Shivaprasad Assignee: Jonathan Maron Attachments: org.apache.atlas.hive.hook.NegativeSSLAndKerberosHiveHookIT.txt -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-67) Validate with secure zookeeper server for titan interaction with hbase and solr
[ https://issues.apache.org/jira/browse/ATLAS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14711694#comment-14711694 ] Jonathan Maron commented on ATLAS-67: - I believe I now have my environment setup correctly and I saw the issue noted above. I believe the issue may have been a combination of: - Requiring a service principal for zookeeper to exist in the keytab files configured for the kerberos tests - Ensuring that the address portion of the generated principals is an IPv4 formatted address I'll submit a patch to review board. If you could download to verify the fix I would appreciate it. Validate with secure zookeeper server for titan interaction with hbase and solr --- Key: ATLAS-67 URL: https://issues.apache.org/jira/browse/ATLAS-67 Project: Atlas Issue Type: Task Reporter: Suma Shivaprasad Attachments: org.apache.atlas.hive.hook.NegativeSSLAndKerberosHiveHookIT.txt -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-67) Validate with secure zookeeper server for titan interaction with hbase and solr
[ https://issues.apache.org/jira/browse/ATLAS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14710007#comment-14710007 ] Jonathan Maron edited comment on ATLAS-67 at 8/24/15 8:35 PM: -- I ran into issues trying to set this up. From the initial indications it appeared that perhaps a local, standalone instance of zookeeper was required. I therefore tried installing that but still saw issues in atlas start up: Caused by: org.apache.solr.common.SolrException: Cannot connect to cluster at 127.0.0.1:2181: cluster not found/not ready at org.apache.solr.common.cloud.ZkStateReader.createClusterStateWatchersAndUpdate(ZkStateReader.java:344) at org.apache.solr.client.solrj.impl.CloudSolrClient.connect(CloudSolrClient.java:458) at com.thinkaurelius.titan.diskstorage.solr.Solr5Index.init(Solr5Index.java:215) ... 105 more 8 errors at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466) at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:184) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:110) at com.google.inject.Guice.createInjector(Guice.java:96) at com.google.inject.Guice.createInjector(Guice.java:73) at com.google.inject.Guice.createInjector(Guice.java:62) at org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:67) at com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47) at org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:106) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294) at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132) at org.eclipse.jetty.server.Server.start(Server.java:387) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61) at org.eclipse.jetty.server.Server.doStart(Server.java:354) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:88) at org.apache.atlas.Main.main(Main.java:105) I've tried various things. My latest attempt was trying to startup solr pointing to local zookeeper, but seeing exceptions such as this in solr log: ERROR - 2015-08-24 20:25:32.407; [ ] org.apache.solr.cloud.ZkController; Could not find configName for collection edge_index ERROR - 2015-08-24 20:25:32.407; [ ] org.apache.solr.cloud.ZkController; Could not find configName for collection fulltext_index ERROR - 2015-08-24 20:25:32.407; [ ] org.apache.solr.cloud.ZkController; Could not find configName for collection vertex_index ERROR - 2015-08-24 20:25:32.409; [ ] org.apache.solr.core.CoreContainer; Error creating core [vertex_index_shard1_replica1]: Could not find configName for collection vertex_index found:null org.apache.solr.common.cloud.ZooKeeperException: Could not find configName for collection vertex_index found:null at org.apache.solr.cloud.ZkController.getConfName(ZkController.java:1419) at org.apache.solr.cloud.ZkController.createCollectionZkNode(ZkController.java:1345) at org.apache.solr.cloud.CloudConfigSetService.createCoreResourceLoader(CloudConfigSetService.java:36) at org.apache.solr.core.ConfigSetService.getConfig(ConfigSetService.java:70) at org.apache.solr.core.CoreContainer.create(CoreContainer.java:635) at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:381) at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:375) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at
[jira] [Resolved] (ATLAS-121) Unable to build on fresh stack
[ https://issues.apache.org/jira/browse/ATLAS-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron resolved ATLAS-121. -- Resolution: Duplicate Unable to build on fresh stack -- Key: ATLAS-121 URL: https://issues.apache.org/jira/browse/ATLAS-121 Project: Atlas Issue Type: Bug Reporter: Vishal Kadam On fresh checkout or doing `mvn clean` before `mvn clean install` fails the build process with following error. Its failing because assembly is looking for a file incubator-atlas/webapp/target/atlas-webapp-0.6-incubating-SNAPSHOT.war which does not exists first time or after mvn clean. OK [INFO] [INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @ apache-atlas --- [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default) @ apache-atlas --- [INFO] Reading assembly descriptor: src/main/assemblies/standalone-package.xml [INFO] Reading assembly descriptor: src/main/assemblies/src-package.xml [INFO] [INFO] Reactor Summary: [INFO] [INFO] apache-atlas ... FAILURE [ 4.786 s] [INFO] Apache Atlas Typesystem SKIPPED [INFO] Apache Atlas Client SKIPPED [INFO] Apache Atlas Notification .. SKIPPED [INFO] Apache Atlas Repository SKIPPED [INFO] Apache Atlas Web Application ... SKIPPED [INFO] Apache Atlas Documentation . SKIPPED [INFO] Apache Atlas Hive Bridge ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.587 s [INFO] Finished at: 2015-08-21T23:32:01-04:00 [INFO] Final Memory: 26M/981M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default) on project apache-atlas: Failed to create assembly: Error adding file to archive: /hortonworks/incubator-atlas/webapp/target/atlas-webapp-0.6-incubating-SNAPSHOT.war isn't a file. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-118) rename atlas log4j configuration files to avoid config collisions with other projects
[ https://issues.apache.org/jira/browse/ATLAS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron resolved ATLAS-118. -- Resolution: Fixed rename atlas log4j configuration files to avoid config collisions with other projects - Key: ATLAS-118 URL: https://issues.apache.org/jira/browse/ATLAS-118 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Jonathan Maron Assignee: Jonathan Maron Fix For: 0.6-incubating Original Estimate: 48h Remaining Estimate: 48h There appear to be instances in which using the default name for log4j configuration (e.g. log4j.xml) will cause the atlas version of the file to be picked up and utilized by other projects (e.g. hive/hcat). This can actually lead to issues with the functionality of other projects, especially if they are dependent on log parsing. The log4j.xml file will be renamed to atlas-log4j.xml and explicitly referenced from the scripts via the 'log4j.configuration' system property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-118) rename atlas log4j configuration files to avoid config collisions with other projects
[ https://issues.apache.org/jira/browse/ATLAS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14705452#comment-14705452 ] Jonathan Maron edited comment on ATLAS-118 at 8/20/15 6:08 PM: --- I disagree. Relying on default behavior makes configuration mismatches much more of an issue - if multiple projects rely on the default behavior, exactly which file will get loaded? The one that's first in the classpath for the given classloader, which is subject to change and yields difficulties in debugging when an issue suddenly manifests with no code change. In addition, this is not a code change. Rather, it is the suggested mechanism from the log4j manual - use the log4.configuration system property to identity the file name to leverage. So all we've really done is ensure that we are reading the configuration we expect and preventing others from loading a configuration they do not expect by being explicit with a file name (added the property to the appropriate scripts). was (Author: jmaron): I disagree. Relying on default behavior makes configuration mismatches much more of an issue - if multiple projects rely on the default behavior, exactly which file will get loaded? The one that's first in the classpath for the given classloader, which is subject to change and yields difficulties in debugging when an issue suddenly manifests with no code change. In addition, this is not a code change. Rather, it is the advised mechanism from the log4j manual - use the log4.configuration system property to identity the file name to leverage. So all we've really done is ensure that we are reading the configuration we expect and preventing others from loading a configuration they do not expect by being explicit with a file name (added the property to the appropriate scripts). rename atlas log4j configuration files to avoid config collisions with other projects - Key: ATLAS-118 URL: https://issues.apache.org/jira/browse/ATLAS-118 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Jonathan Maron Assignee: Jonathan Maron Fix For: 0.6-incubating Original Estimate: 48h Remaining Estimate: 48h There appear to be instances in which using the default name for log4j configuration (e.g. log4j.xml) will cause the atlas version of the file to be picked up and utilized by other projects (e.g. hive/hcat). This can actually lead to issues with the functionality of other projects, especially if they are dependent on log parsing. The log4j.xml file will be renamed to atlas-log4j.xml and explicitly referenced from the scripts via the 'log4j.configuration' system property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-118) rename atlas log4j configuration files to avoid config collisions with other projects
Jonathan Maron created ATLAS-118: Summary: rename atlas log4j configuration files to avoid config collisions with other projects Key: ATLAS-118 URL: https://issues.apache.org/jira/browse/ATLAS-118 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Jonathan Maron Assignee: Jonathan Maron Fix For: 0.6-incubating There appear to be instances in which using the default name for log4j configuration (e.g. log4j.xml) will cause the atlas version of the file to be picked up and utilized by other projects (e.g. hive/hcat). This can actually lead to issues with the functionality of other projects, especially if they are dependent on log parsing. The log4j.xml file will be renamed to atlas-log4j.xml and explicitly referenced from the scripts via the 'log4j.configuration' system property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-85) ./dashboard/v2/npm-debug.log file should be added into rat exclusion list
[ https://issues.apache.org/jira/browse/ATLAS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649204#comment-14649204 ] Jonathan Maron commented on ATLAS-85: - Should we consider removing rat from the default profile? ./dashboard/v2/npm-debug.log file should be added into rat exclusion list - Key: ATLAS-85 URL: https://issues.apache.org/jira/browse/ATLAS-85 Project: Atlas Issue Type: Bug Reporter: Chen He On Mac, with OSX Yosemite 10.10.0.2 and node.js installed INFO] apache-atlas ... FAILURE [ 2.746 s] [INFO] Apache Atlas Typesystem SKIPPED [INFO] Apache Atlas Client SKIPPED [INFO] Apache Atlas Repository SKIPPED [INFO] Apache Atlas Web Application ... SKIPPED [INFO] Apache Atlas Documentation . SKIPPED [INFO] Apache Atlas Hive Bridge ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.893 s [INFO] Finished at: 2015-07-24T14:26:35-07:00 [INFO] Final Memory: 28M/319M [INFO] [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check (rat-check) on project apache-atlas: Too many unapproved licenses: 1 - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException Tried with -Dlicense.skip=true or -Dlicensing or Drat.numUnapprovedLicense=100, none of them works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-56) atlas_config.py should give an informative error if jar or java binaries can't be found
[ https://issues.apache.org/jira/browse/ATLAS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14633960#comment-14633960 ] Jonathan Maron commented on ATLAS-56: - I think the test is valid for guarding against a regression. The patch looks good to me. atlas_config.py should give an informative error if jar or java binaries can't be found --- Key: ATLAS-56 URL: https://issues.apache.org/jira/browse/ATLAS-56 Project: Atlas Issue Type: Improvement Affects Versions: trunk Reporter: Aaron Dossett Assignee: Aaron Dossett Priority: Minor Fix For: trunk Attachments: ATLAS-56.patch, ATLAS-56_2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-46) Different data directory with restart
[
https://issues.apache.org/jira/browse/ATLAS-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629919#comment-14629919
]
Jonathan Maron commented on ATLAS-46:
-
What I propose is that we pre-process the variables/tokens before passing the
configuration properties on to titan etc.
Different data directory with restart
-
Key: ATLAS-46
URL: https://issues.apache.org/jira/browse/ATLAS-46
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
Priority: Critical
Fix For: trunk
Attachments: ATLAS-46.patch, application.log
Atlas start picks up different data directories - initially
./server/webapp/atlas/data and after restart ./data. This must be because of
relative path in the configuration
{noformat}
apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep -i atlas
504 6437 1 0 11:51AM ttys0000:07.66
/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java
-Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
-Datlas.log.file=application.log
-Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
-Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
-Xmx1024m -classpath
/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
org.apache.atlas.Main -app
/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
./server/webapp/atlas/data
./server/webapp/atlas/data/es/data
./server/webapp/atlas/lib/jquery/src/data
apache-atlas-0.6-incubating-SNAPSHOT$ ./bin/atlas_stop.py
apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep atlas
504 6457 1 0 11:54AM ttys0000:07.50
/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java
-Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
-Datlas.log.file=application.log
-Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
-Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
-Xmx1024m -classpath
/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
org.apache.atlas.Main -app
/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
./data
./data/es/data
./server/webapp/atlas/data
./server/webapp/atlas/data/es/data
./server/webapp/atlas/lib/jquery/src/data
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-46) Different data directory with restart
[
https://issues.apache.org/jira/browse/ATLAS-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628428#comment-14628428
]
Jonathan Maron commented on ATLAS-46:
-
Would a full path for the properties in the application.properties file work?
In that instance perhaps we could provide for tokens and do the substitution
during initialization, e.g.:
atlas.graph.storage.directory=${atlas.home}/data/berkley
where atlas.home represents one of the defined tokens or alternatively is the
name of a system property or command line option? That may provide for more
flexibility.
Different data directory with restart
-
Key: ATLAS-46
URL: https://issues.apache.org/jira/browse/ATLAS-46
Project: Atlas
Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
Priority: Critical
Fix For: trunk
Attachments: ATLAS-46.patch, application.log
Atlas start picks up different data directories - initially
./server/webapp/atlas/data and after restart ./data. This must be because of
relative path in the configuration
{noformat}
apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep -i atlas
504 6437 1 0 11:51AM ttys0000:07.66
/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java
-Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
-Datlas.log.file=application.log
-Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
-Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
-Xmx1024m -classpath
/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
org.apache.atlas.Main -app
/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
./server/webapp/atlas/data
./server/webapp/atlas/data/es/data
./server/webapp/atlas/lib/jquery/src/data
apache-atlas-0.6-incubating-SNAPSHOT$ ./bin/atlas_stop.py
apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep atlas
504 6457 1 0 11:54AM ttys0000:07.50
/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java
-Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
-Datlas.log.file=application.log
-Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
-Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
-Xmx1024m -classpath
/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
org.apache.atlas.Main -app
/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
./data
./data/es/data
./server/webapp/atlas/data
./server/webapp/atlas/data/es/data
./server/webapp/atlas/lib/jquery/src/data
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-71) define an API for allowing the registration of a metrics handler (sink)
Jonathan Maron created ATLAS-71: --- Summary: define an API for allowing the registration of a metrics handler (sink) Key: ATLAS-71 URL: https://issues.apache.org/jira/browse/ATLAS-71 Project: Atlas Issue Type: Task Reporter: Jonathan Maron A mechanism is required to be defined for registration of a metrics handler that can be leveraged by metrics collection systems such as AMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-70) Metrics need to be defined and published to enhance atlas service management
Jonathan Maron created ATLAS-70: --- Summary: Metrics need to be defined and published to enhance atlas service management Key: ATLAS-70 URL: https://issues.apache.org/jira/browse/ATLAS-70 Project: Atlas Issue Type: Improvement Reporter: Jonathan Maron The metrics that make sense for understanding the operational health and status of the atlas server need to be defined and published using appropriate APIs etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-68) Security tests failing with Hbase
[
https://issues.apache.org/jira/browse/ATLAS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14625003#comment-14625003
]
Jonathan Maron commented on ATLAS-68:
-
It would help if these bugs included the steps to reproduce the issue locally.
Thanks!
Security tests failing with Hbase
--
Key: ATLAS-68
URL: https://issues.apache.org/jira/browse/ATLAS-68
Project: Atlas
Issue Type: Task
Reporter: Suma Shivaprasad
Attachments:
org.apache.atlas.web.service.SecureEmbeddedServerIT-output.txt
{noformat}
2015-07-13 20:28:41,051 INFO - [main:] ~ Stopped
SslSocketConnector@0.0.0.0:21443 (log:67)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:129)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:113)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
2015-07-13 20:28:39,686 INFO - [main:] ~ Started
SslSocketConnector@0.0.0.0:21443 (log:67)
[TestNG] Running:
Command line suite
typesAsJSON = {
enumTypes:[
],
structTypes:[
{
superTypes:[
],
hierarchicalMetaTypeName:org.apache.atlas.typesystem.types.ClassType,
typeName:database,
attributeDefinitions:[
{
Caused by: java.lang.RuntimeException: class
org.apache.hadoop.hbase.client.ClusterStatusListener$MulticastListener not
org.apache.hadoop.hbase.client.ClusterStatusListener$Listener
at
org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2100)
... 134 more
8 errors
at
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466)
at
com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:184)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:110)
at com.google.inject.Guice.createInjector(Guice.java:96)
at com.google.inject.Guice.createInjector(Guice.java:73)
at com.google.inject.Guice.createInjector(Guice.java:62)
at
org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:67)
at
com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
at
org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:106)
at
org.apache.atlas.web.listeners.TestGuiceServletConfig.contextInitialized(TestGuiceServletConfig.java:38)
at
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.apache.atlas.web.service.SecureEmbeddedServerITBase.runOtherSuitesAgainstSecureServer(SecureEmbeddedServerITBase.java:166)
at
[jira] [Commented] (ATLAS-52) Merge client.properties and application.properties
[ https://issues.apache.org/jira/browse/ATLAS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14621077#comment-14621077 ] Jonathan Maron commented on ATLAS-52: - I'm not certain we're talking about the same thing. Let me take a concrete example: The server configures a property to indicate the HTTP listener port. Let's say it's called 'atlas.server.http.port'. Perhaps the client needs that port value for establishing a connection. Should its properties file have some other named property for the HTTP server port, or should the client use a similarly named property in its configuration/properties file? (Remember - this is just illustrative. I understand that the client may not need to know the server's HTTP port). The issue of keeping files in synch is more of an operational, cluster control issue, somewhat independent of the actual names of the properties or the content. Merge client.properties and application.properties -- Key: ATLAS-52 URL: https://issues.apache.org/jira/browse/ATLAS-52 Project: Atlas Issue Type: Task Reporter: Shwetha G S Assignee: Shwetha G S -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-56) atlas_config.py should give an informative error if jar or java binaries can't be found
[ https://issues.apache.org/jira/browse/ATLAS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14620582#comment-14620582 ] Jonathan Maron commented on ATLAS-56: - Just for completeness sake, perhaps there's a way to test this functionality via the python unit test (TestMetadata.py)? atlas_config.py should give an informative error if jar or java binaries can't be found --- Key: ATLAS-56 URL: https://issues.apache.org/jira/browse/ATLAS-56 Project: Atlas Issue Type: Improvement Affects Versions: trunk Reporter: Aaron Dossett Priority: Minor Fix For: trunk Attachments: ATLAS-56.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-29) client authentication fails in secure environment from server processes
Jonathan Maron created ATLAS-29: --- Summary: client authentication fails in secure environment from server processes Key: ATLAS-29 URL: https://issues.apache.org/jira/browse/ATLAS-29 Project: Atlas Issue Type: Bug Affects Versions: 0.5-incubating Reporter: Jonathan Maron Assignee: Jonathan Maron Fix For: 0.5-incubating During client invocations in secure environments the invocation may fail with exceptions such as: Caused by: org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-29) client authentication fails in secure environment from server processes
[ https://issues.apache.org/jira/browse/ATLAS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14592690#comment-14592690 ] Jonathan Maron commented on ATLAS-29: - It is 0.5-incubating client authentication fails in secure environment from server processes --- Key: ATLAS-29 URL: https://issues.apache.org/jira/browse/ATLAS-29 Project: Atlas Issue Type: Bug Affects Versions: 0.5-incubating Reporter: Jonathan Maron Assignee: Jonathan Maron Fix For: 0.5-incubating Original Estimate: 24h Remaining Estimate: 24h During client invocations in secure environments the invocation may fail with exceptions such as: Caused by: org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-19) remove docs associated with python mock used for testing
Jonathan Maron created ATLAS-19: --- Summary: remove docs associated with python mock used for testing Key: ATLAS-19 URL: https://issues.apache.org/jira/browse/ATLAS-19 Project: Atlas Issue Type: Bug Reporter: Jonathan Maron Assignee: Jonathan Maron The docs provided with the mock are superfluous to the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
