You can spill to disk in case maximum memory per node limit is crossed.   https://docs.qubole.com/en/latest/admin-guide/engine-admin/presto-admin/spill-disk-config.html   Hope it helps! ... View more

Hello，I met the same question as yours, but I really dont understand what the links say in your posts, could I get your explaination? just add the value of atlas.rest.address can solve this problem? But I have already add atlas.rest.address = <Atlas-host>:<port> property to atlas-application.properties，By the way, I am using atlas 1.2.0 Here is my atlas-application.properties: atlas.graph.storage.backend=hbase atlas.graph.storage.hbase.table=apache_atlas_janus atlas.graph.storage.hostname=gaoenwei66.cmp3481.interconnect,gaoenwei67.cmp3481.interconnect,gaoenwei65.cmp3481.interconnect atlas.graph.storage.hbase.regions-per-server=1 atlas.graph.storage.lock.wait-time=10000 atlas.EntityAuditRepository.impl=org.apache.atlas.repository.audit.HBaseBasedAuditRepository atlas.graph.index.search.backend=elasticsearch atlas.graph.index.search.index-name=es_janusgraph atlas.graph.index.search.hostname=gaoenwei70.cmp3481.interconnect,gaoenwei68.cmp3481.interconnect,gaoenwei65.cmp3481.interconnect atlas.graph.index.search.elasticsearch.client-only=true atlas.graph.index.search.max-result-set-size=150 atlas.notification.embedded=false #atlas.kafka.data=${sys:atlas.home}/data/kafka atlas.kafka.zookeeper.connect=gaoenwei67.cmp3481.interconnect:2181,gaoenwei66.cmp3481.interconnect:2181,gaoenwei65.cmp3481.interconnect:2181 atlas.kafka.bootstrap.servers=gaoenwei67.cmp3481.interconnect:2181,gaoenwei66.cmp3481.interconnect:2181,gaoenwei65.cmp3481.interconnect:9092 atlas.kafka.zookeeper.session.timeout.ms=400 atlas.kafka.zookeeper.connection.timeout.ms=200 atlas.kafka.zookeeper.sync.time.ms=20 atlas.kafka.auto.commit.interval.ms=1000 atlas.kafka.hook.group.id=atlas atlas.kafka.enable.auto.commit=false atlas.kafka.auto.offset.reset=earliest atlas.kafka.session.timeout.ms=30000 atlas.kafka.offsets.topic.replication.factor=2 atlas.kafka.poll.timeout.ms=1000 atlas.notification.hook.topic.name=ATLAS_HOOK atlas.notification.entities.topic.name=ATLAS_ENTITIES atlas.notification.hook.consumer.topic.names=ATLAS_HOOK atlas.notification.entities.consumer.topic.names=ATLAS_ENTITIES atlas.notification.create.topics=false atlas.notification.replicas=2 atlas.notification.topics=ATLAS_HOOK,ATLAS_ENTITIES atlas.notification.log.failed.messages=true atlas.notification.consumer.retry.interval=500 atlas.notification.hook.retry.interval=1000 atlas.enableTLS=false atlas.authentication.method.kerberos=false atlas.authentication.method.file=true #### ldap.type= LDAP or AD atlas.authentication.method.ldap.type=none #### user credentials file atlas.authentication.method.file.filename=${sys:atlas.home}/conf/users-credentials.properties atlas.rest.address=http://172.21.42.78:21000/ # If enabled and set to true, this will run setup steps when the server starts atlas.server.run.setup.on.start=false atlas.audit.hbase.tablename=apache_atlas_entity_audit atlas.audit.zookeeper.session.timeout.ms=1000 atlas.audit.hbase.zookeeper.quorum=gaoenwei66.cmp3481.interconnect,gaoenwei67.cmp3481.interconnect,gaoenwei65.cmp3481.interconnect:2181 atlas.server.ha.enabled=false atlas.authorizer.impl=simple atlas.authorizer.simple.authz.policy.file=atlas-simple-authz-policy.json atlas.rest-csrf.enabled=true atlas.rest-csrf.browser-useragents-regex=^Mozilla.*,^Opera.*,^Chrome.* atlas.rest-csrf.methods-to-ignore=GET,OPTIONS,HEAD,TRACE atlas.rest-csrf.custom-header=X-XSRF-HEADER atlas.metric.query.cache.ttlInSecs=900 atlas.search.gremlin.enable=false atlas.hook.hive.synchronous=false atlas.hook.hive.numRetries=3 atlas.hook.hive.queueSize=10000 atlas.cluster.name=primary atlas.hook.hbase.synchronous=false atlas.hook.hbase.numRetries=3 atlas.hook.hbase.queueSize=10000 atlas.cluster.name=primary   I really need your help, wish for your answer  ... View more

@asmarz, As this is an older thread which was previously marked 'Solved', you would have a better chance of receiving a resolution by starting a new thread. This will also provide the opportunity to provide details specific to your environment (for example, what happened once you added the affected user accounts with "normal" command add user on all nodes)  that could aid others in providing a more relevant, accurate answer to your question.     ... View more

This was a good stuff and you have explained the The HDF and HDP are two separate product lines each being managed by its own Ambari installation. You have done a great job here and the way you explained it was really appreciable. You can use display stands in dubai to get more valuable updates and information ... View more

@Sagar Shimpi Thanks it worked. ... View more