atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ATLAS-67) Validate with secure zookeeper server for titan interaction with hbase and solr
Date Tue, 25 Aug 2015 04:01:46 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710537#comment-14710537
] 

Suma Shivaprasad edited comment on ATLAS-67 at 8/25/15 4:01 AM:
----------------------------------------------------------------

Jon,

1. Once you start Solr in cloud mode, it also starts zookeeper in embedded mode on port 9983.
So , if you edit pom.xml in the distributed profile to have solr.zk.address=localhost:9983,
it should connect to the embedded ZK and should work. Hbase in standalone mode starts up en
embedded zookeeper on 2181 port. You should be able to see these in the logs.
2. Once you start Solr as bin/solr -c, you need to create collections for vertex_index, edge_index,
fulltext_index as mentioned in InstallationSteps.twiki - section "Configuring SOLR as the
Indexing Backend for the Graph Repository".. as bin/solr create -c...... From the above stack
trace it appears they were not created. Once the collections are created, you can verify that
they are in Zookeeper under /collections/ node. 
3. There is no need for a separate instance of ATLAS setup
4. wrt this java.lang.VerifyError: Bad type on operand stack, I dont see this occuring now
in my box. Used to occur sometime back. Let me see if I can reproduce this. Also pls let me
know if its occuring even after the above 3 steps.








was (Author: suma.shivaprasad):
Jon,

1. Once you start Solr in cloud mode, it also starts zookeeper in embedded mode on port 9983.
So , if you edit pom.xml in the distributed profile to have solr.zk.address=localhost:9983,
it should connect to the embedded ZK and should work. Hbase in standalone mode starts up en
embedded zookeeper on 2181 port. You should be able to see these in the logs.
2. Once you start Solr as bin/solr -c, you need to create collections for vertex_index, edge_index,
fulltext_index as mentioned in InstallationSteps.twiki - section "Configuring SOLR as the
Indexing Backend for the Graph Repository".. as bin/solr create -c...... From the above stack
trace it appears they were not created.
3. There is no need for a separate instance of ATLAS setup
4. wrt this java.lang.VerifyError: Bad type on operand stack, I dont see this occuring now
in my box. Used to occur sometime back. Let me see if I can reproduce this. Also pls let me
know if its occuring even after the above 3 steps.







> 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)

Mime
View raw message