Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Atlas Server fails to start on HDP 2.5 Sandbox on Docker

avatar
New Contributor

Hello all,

I have previously had success working with Apache Atlas within the Sandbox using Docker, but on a fresh install, I've come across the following issue I cannot resolve.

Environment:

  • A new container running the HDP docker image locally, Docker 1.13.0 on El Capitan (10.11.6).
  • All default services are running
  • Kafka, Ambari Infra, and HBase and have been started and confirmed to be running.
  • Attempts to start Atlas consistently fail with the following error:
stderr:   /var/lib/ambari-agent/data/errors-187.txt
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py", line 217, in <module>
    MetadataServer().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 280, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py", line 94, in start
    user=params.hbase_user
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__
    self.env.run()
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run
    self.run_action(resource, action)
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action
    provider_action()
  File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 273, in action_run
    tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 71, in inner
    result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 93, in checked_call
    tries=tries, try_sleep=try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 141, in _call_wrapper
    result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 294, in _call
    raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'cat /var/lib/ambari-agent/tmp/atlas_hbase_setup.rb | hbase shell -n' returned 1. atlas_titan
ATLAS_ENTITY_AUDIT_EVENTS
atlas
TABLE
atlas_titan
1 row(s) in 0.3290 seconds

nil
TABLE
atlas_titan
1 row(s) in 0.0020 seconds

nil
ERROR ArgumentError: DISABLED: Security features are not available

Trying to debug from HBase, I see the following:

hbase(main):001:0> list

TABLE
atlas_titan
1 row(s) in 0.1710 seconds

=> ["atlas_titan"

So it seems that creating ATLAS_ENTITY_AUDIT_EVENTS fails, but when I attempt to do so manually:

hbase(main):002:0> create 'ATLAS_ENTITY_AUDIT_EVENTS', {NAME => 'dt', DATA_BLOCK_ENCODING => 'FAST_DIFF', COMPRESSION =>'GZ', BLOOMFILTER =>'ROW'}

ERROR: Table already exists: ATLAS_ENTITY_AUDIT_EVENTS!

However:

hbase(main):002:0> exists 'ATLAS_ENTITY_AUDIT_EVENTS'
Table ATLAS_ENTITY_AUDIT_EVENTS does not exist
0 row(s) in 0.0780 seconds

I am uncertain how to proceed; any help would be greatly appreciated!

1 ACCEPTED SOLUTION

avatar
@nick _

It is possible that zookeeper has that corresponding znode for that table and restricting to create the table. So, I would suggest, open the zookeeper client terminal and delete the hbase table znode entry using this command "rmr /hbase/table/TABLE_NAME" .

After that restart hbase service(both master+region servers) and try recreating the table. This should resolve the issue.

View solution in original post

4 REPLIES 4

avatar
@nick _

It is possible that zookeeper has that corresponding znode for that table and restricting to create the table. So, I would suggest, open the zookeeper client terminal and delete the hbase table znode entry using this command "rmr /hbase/table/TABLE_NAME" .

After that restart hbase service(both master+region servers) and try recreating the table. This should resolve the issue.

avatar
@nick _

Did you try the mentioned solution? Is it working for you?

avatar
New Contributor

Hi Ayub,

Apologies for the delayed response. Your solution did in fact resolve this curious issue. Thanks again!

avatar

Glad it worked! Accept the answer.