Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apache atlas initialization fails in VDC chart #3

Closed
planetf1 opened this issue Sep 8, 2020 · 2 comments
Closed

Apache atlas initialization fails in VDC chart #3

planetf1 opened this issue Sep 8, 2020 · 2 comments
Assignees

Comments

@planetf1
Copy link
Member

planetf1 commented Sep 8, 2020

The apache atlas jobs container fails to start - showing:

vdc-odpi-egeria-vdc-job-04-init-apache-atlas-tvdf7      0/1     Init:0/3    0          17m

and we can see the first task is to check the service is running -- but logging into the atlas container what we find is:

bash-4.4$ cat logs/*err
Picked up JAVA_TOOL_OPTIONS: -Xmx1024m
INFO  - 2020-09-08 16:37:08.602; org.apache.solr.util.configuration.SSLCredentialProviderFactory; Processing SSL Credential Provider chain: env;sysprop

ERROR: Failed to create collection 'vertex_index' due to: {192.168.2.12:9838_solr=org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:Error from server at http://192.168.2.12:9838/solr: Error CREATEing SolrCore 'vertex_index_shard1_replica_n1': Unable to create core [vertex_index_shard1_replica_n1] Caused by: no segments* file found in LockValidatingDirectoryWrapper(NRTCachingDirectory(MMapDirectory@/opt/apache/atlas/solr/server/solr/vertex_index_shard1_replica_n1/data/index lockFactory=org.apache.lucene.store.NativeFSLockFactory@6f6cbc6c; maxCacheMB=48.0 maxMergeSizeMB=4.0)): files: [write.lock]}

Picked up JAVA_TOOL_OPTIONS: -Xmx1024m
INFO  - 2020-09-08 16:37:49.906; org.apache.solr.util.configuration.SSLCredentialProviderFactory; Processing SSL Credential Provider chain: env;sysprop

ERROR: Failed to create collection 'edge_index' due to: {192.168.2.12:9838_solr=org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:Error from server at http://192.168.2.12:9838/solr: Error CREATEing SolrCore 'edge_index_shard1_replica_n1': Unable to create core [edge_index_shard1_replica_n1] Caused by: no segments* file found in LockValidatingDirectoryWrapper(NRTCachingDirectory(MMapDirectory@/opt/apache/atlas/solr/server/solr/edge_index_shard1_replica_n1/data/index lockFactory=org.apache.lucene.store.NativeFSLockFactory@6f6cbc6c; maxCacheMB=48.0 maxMergeSizeMB=4.0)): files: [write.lock]}

Picked up JAVA_TOOL_OPTIONS: -Xmx1024m
INFO  - 2020-09-08 16:38:23.923; org.apache.solr.util.configuration.SSLCredentialProviderFactory; Processing SSL Credential Provider chain: env;sysprop

ERROR: Failed to create collection 'fulltext_index' due to: {192.168.2.12:9838_solr=org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:Error from server at http://192.168.2.12:9838/solr: Error CREATEing SolrCore 'fulltext_index_shard1_replica_n1': Unable to create core [fulltext_index_shard1_replica_n1] Caused by: no segments* file found in LockValidatingDirectoryWrapper(NRTCachingDirectory(MMapDirectory@/opt/apache/atlas/solr/server/solr/fulltext_index_shard1_replica_n1/data/index lockFactory=org.apache.lucene.store.NativeFSLockFactory@6f6cbc6c; maxCacheMB=48.0 maxMergeSizeMB=4.0)): files: [write.lock]}

Picked up JAVA_TOOL_OPTIONS: -Xmx1024m

It looks as if solr has problems - even in this clean environment. This may mean we have a bad atlas build, or need to do some updates.

Either way the vdc environment is incomplete. The most appropriate action appears to be to disable until fixed.

@planetf1 planetf1 self-assigned this Sep 16, 2020
@planetf1 planetf1 transferred this issue from odpi/egeria Sep 18, 2020
@planetf1
Copy link
Member Author

planetf1 commented Mar 8, 2021

Putting this on hold until we've completed refactoring around samples/security/ranger and figured out where we want to go next with vdc.

If you are dependent on the vdc chart and need to get it working please comment here and I'll look at it sooner

@planetf1
Copy link
Member Author

The VDC environment will need significant re-work to adapt to the many changes made in Egeria to better support
metadata integration. Additionally the helm charts used for the lab & a simple base config have evolved to better support
different types of services, exposing of ports, persistent storage etc.

As such specific incremental changes to the current - now old - charts do not really add value.

As such closing for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant