qidao123.com ToB IT社区-企服评测·应用市场»论坛 › 物联网/工业互联网 › 物联网 › APACHE-ATLAS-2.1.0 - 根本运维

APACHE-ATLAS-2.1.0 - 根本运维

[复制链接]
发表于 2026-1-25 02:54:54 | 显示全部楼层 |阅读模式

马上注册，结交更多好友，享用更多功能，让你轻松玩转社区。

您需要 登录 才可以下载或查看，没有账号？立即注册

×
（一）SOLR相干

1. 怎样创建/删除聚集？
  1. # 1. 删除
  2. solr/bin/solr delete -c vertex_index
  3. solr/bin/solr delete -c edge_index
  4. solr/bin/solr delete -c fulltext_index
  6. # 2. 创建
  7. solr/bin/solr create -c vertex_index -force -d conf/solr/
  8. solr/bin/solr create -c edge_index -force -d conf/solr/
  9. solr/bin/solr create -c fulltext_index -force -d conf/solr/
  11. # 删除
  12. [root@master apache-atlas-2.1.0]# solr/bin/solr delete -c vertex_index
  13. INFO  - 2023-06-15 00:19:40.690; org.apache.solr.util.configuration.SSLCredentialProviderFactory; Processing SSL Credential Provider chain: env;sysprop
  14. {"responseHeader":{
  15.     "status":0,
  16.     "QTime":835}}
  17. Deleted collection 'vertex_index' using command:
  18. http://192.168.118.174:8983/solr/admin/collections?action=DELETE&name=vertex_index
  19. [root@master apache-atlas-2.1.0]# solr/bin/solr delete -c edge_index
  20. INFO  - 2023-06-15 00:19:44.906; org.apache.solr.util.configuration.SSLCredentialProviderFactory; Processing SSL Credential Provider chain: env;sysprop
  21. {"responseHeader":{
  22.     "status":0,
  23.     "QTime":634}}
  24. Deleted collection 'edge_index' using command:
  25. http://192.168.118.174:8983/solr/admin/collections?action=DELETE&name=edge_index
  26. [root@master apache-atlas-2.1.0]# solr/bin/solr delete -c fulltext_index
  27. INFO  - 2023-06-15 00:19:52.255; org.apache.solr.util.configuration.SSLCredentialProviderFactory; Processing SSL Credential Provider chain: env;sysprop
  28. {"responseHeader":{
  29.     "status":0,
  30.     "QTime":707}}
  31. Deleted collection 'fulltext_index' using command:
  32. http://192.168.118.174:8983/solr/admin/collections?action=DELETE&name=fulltext_index
  33. [root@master apache-atlas-2.1.0]#
  34. # 创建
  35. [root@master apache-atlas-2.1.0]# solr/bin/solr create -c vertex_index -force -d conf/solr/
  36. INFO  - 2023-06-15 00:20:04.079; org.apache.solr.util.configuration.SSLCredentialProviderFactory; Processing SSL Credential Provider chain: env;sysprop
  37. Created collection 'vertex_index' with 1 shard(s), 1 replica(s) with config-set 'vertex_index'
  38. [root@master apache-atlas-2.1.0]# solr/bin/solr create -c edge_index -force -d conf/solr/
  39. INFO  - 2023-06-15 00:20:13.817; org.apache.solr.util.configuration.SSLCredentialProviderFactory; Processing SSL Credential Provider chain: env;sysprop
  40. Created collection 'edge_index' with 1 shard(s), 1 replica(s) with config-set 'edge_index'
  41. [root@master apache-atlas-2.1.0]# solr/bin/solr create -c fulltext_index -force -d conf/solr/
  42. INFO  - 2023-06-15 00:20:21.018; org.apache.solr.util.configuration.SSLCredentialProviderFactory; Processing SSL Credential Provider chain: env;sysprop
  43. Created collection 'fulltext_index' with 1 shard(s), 1 replica(s) with config-set 'fulltext_index'
  44. [root@master apache-atlas-2.1.0]#
复制代码
2. SOLR的日记在那里？
  1. /opt/rills/software/apache-atlas-2.1.0/solr/server/logs/solr.log
复制代码
（二）HBASE相干

1. 内置的HBASE无法启动

错误信息如下：
java.lang.IllegalStateException: The procedure WAL relies on the ability to hsync for proper operation during component failures
  1. 2023-06-15 09:06:28,071 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181] server.ZooKeeperServer: Client attempting to establish new session at /0:0:0:0:0:0:0:1:55222
  2. 2023-06-15 09:06:28,076 INFO  [SyncThread:0] server.ZooKeeperServer: Established session 0x188bc96d4a90002 with negotiated timeout 10000 for client /0:0:0:0:0:0:0:1:55222
  3. 2023-06-15 09:06:28,076 INFO  [ReadOnlyZKClient-localhost:2181@0x79f2feba-SendThread(localhost:2181)] zookeeper.ClientCnxn: Session establishment complete on server localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x188bc96d4a90002, negotiated timeout = 10000
  4. 2023-06-15 09:06:28,207 INFO  [Thread-22] procedure2.ProcedureExecutor: Starting 16 core workers (bigger of cpus/4 or 16) with max (burst) worker count=160
  5. 2023-06-15 09:06:28,214 WARN  [Thread-22] wal.WALProcedureStore: Remove uninitialized log: DeprecatedRawLocalFileStatus{path=file:/opt/rills/software/apache-atlas-2.1.0/data/hbase-root/MasterProcWALs/pv2-00000000000000000002.log; isDirectory=false; length=0; replication=1; blocksize=33554432; modification_time=1686790826000; access_time=0; owner=; group=; permission=rw-rw-rw-; isSymlink=false}
  6. 2023-06-15 09:06:28,215 INFO  [Thread-22] wal.ProcedureWALFile: Archiving file:/opt/rills/software/apache-atlas-2.1.0/data/hbase-root/MasterProcWALs/pv2-00000000000000000002.log to file:/opt/rills/software/apache-atlas-2.1.0/data/hbase-root/oldWALs/pv2-00000000000000000002.log
  7. 2023-06-15 09:06:28,275 ERROR [Thread-22] master.HMaster: Failed to become active master
  8. java.lang.IllegalStateException: The procedure WAL relies on the ability to hsync for proper operation during component failures, but the underlying filesystem does not support doing so. Please check the config value of 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount that can provide it.
  9.         at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1044)
  10.         at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:383)
  11.         at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:649)
  12.         at org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1282)
  13.         at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:842)
  14.         at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2086)
  15.         at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:553)
  16.         at java.lang.Thread.run(Thread.java:748)
  17. 2023-06-15 09:06:28,276 ERROR [Thread-22] master.HMaster: ***** ABORTING master master,61500,1686791181740: Unhandled exception. Starting shutdown. *****
  18. java.lang.IllegalStateException: The procedure WAL relies on the ability to hsync for proper operation during component failures, but the underlying filesystem does not support doing so. Please check the config value of 'hbase.procedure.store.wal.use.hsync' to set the desired level of robustness and ensure the config value of 'hbase.wal.dir' points to a FileSystem mount that can provide it.
  19.         at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.rollWriter(WALProcedureStore.java:1044)
  20.         at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.recoverLease(WALProcedureStore.java:383)
  21.         at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:649)
  22.         at org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1282)
  23.         at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:842)
  24.         at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2086)
  25.         at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:553)
  26.         at java.lang.Thread.run(Thread.java:748)
  27. 2023-06-15 09:06:28,277 INFO  [Thread-22] regionserver.HRegionServer: ***** STOPPING region server 'master,61500,1686791181740' *****
  28. 2023-06-15 09:06:28,277 INFO  [Thread-22] regionserver.HRegionServer: STOPPED: Stopped by Thread-22
  29. 2023-06-15 09:06:28,841 INFO  [master/master:61500.splitLogManager..Chore.1] hbase.ScheduledChore: Chore: SplitLogManager Timeout Monitor was stopped
  30. 2023-06-15 09:06:30,484 INFO  [M:0;master:61500] ipc.NettyRpcServer: Stopping server on /192.168.118.174:61500
  31. 2023-06-15 09:06:30,497 INFO  [M:0;master:61500] regionserver.HRegionServer: Stopping infoServer
  32. 2023-06-15 09:06:30,538 INFO  [M:0;master:61500] handler.ContextHandler: Stopped o.e.j.w.WebAppContext@67440de6{/,null,UNAVAILABLE}{file:/opt/rills/software/apache-atlas-2.1.0/hbase/hbase-webapps/master}
  33. 2023-06-15 09:06:30,545 INFO  [M:0;master:61500] server.AbstractConnector: Stopped ServerConnector@3910fe11{HTTP/1.1,[http/1.1]}{0.0.0.0:61510}
  34. 2023-06-15 09:06:30,547 INFO  [M:0;master:61500] handler.ContextHandler: Stopped o.e.j.s.ServletContextHandler@5af97169{/static,file:///opt/rills/software/apache-atlas-2.1.0/hbase/hbase-webapps/static/,UNAVAILABLE}
  35. 2023-06-15 09:06:30,547 INFO  [M:0;master:61500] handler.ContextHandler: Stopped o.e.j.s.ServletContextHandler@57adfab0{/logs,file:///opt/rills/software/apache-atlas-2.1.0/hbase/logs/,UNAVAILABLE}
  36. 2023-06-15 09:06:30,549 INFO  [M:0;master:61500] regionserver.HRegionServer: stopping server master,61500,1686791181740
  37. 2023-06-15 09:06:30,549 INFO  [M:0;master:61500] zookeeper.ReadOnlyZKClient: Close zookeeper connection 0x79f2feba to localhost:2181
  38. 2023-06-15 09:06:30,551 INFO  [ProcessThread(sid:0 cport:2181):] server.PrepRequestProcessor: Processed session termination for sessionid: 0x188bc96d4a90002
  39. 2023-06-15 09:06:30,553 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181] server.NIOServerCnxn: Closed socket connection for client /0:0:0:0:0:0:0:1:55222 which had sessionid 0x188bc96d4a90002
  40. 2023-06-15 09:06:30,554 INFO  [ReadOnlyZKClient-localhost:2181@0x79f2feba] zookeeper.ZooKeeper: Session: 0x188bc96d4a90002 closed
  41. 2023-06-15 09:06:30,554 INFO  [ReadOnlyZKClient-localhost:2181@0x79f2feba-EventThread] zookeeper.ClientCnxn: EventThread shut down for session: 0x188bc96d4a90002
  42. 2023-06-15 09:06:30,558 INFO  [M:0;master:61500] regionserver.HRegionServer: stopping server master,61500,1686791181740; all regions closed.
  43. 2023-06-15 09:06:30,558 INFO  [M:0;master:61500] hbase.ChoreService: Chore service for: master/master:61500 had [] on shutdown
  44. 2023-06-15 09:06:30,559 WARN  [M:0;master:61500] master.ActiveMasterManager: Failed get of master address: java.io.IOException: Can't get master address from ZooKeeper; znode data == null
  45. 2023-06-15 09:06:30,561 INFO  [M:0;master:61500] wal.WALProcedureStore: Stopping the WAL Procedure Store, isAbort=false
  46. 2023-06-15 09:06:30,562 INFO  [M:0;master:61500] hbase.ChoreService: Chore service for: master/master:61500.splitLogManager. had [] on shutdown
  47. 2023-06-15 09:06:30,563 INFO  [ProcessThread(sid:0 cport:2181):] server.PrepRequestProcessor: Got user-level KeeperException when processing sessionid:0x188bc96d4a90000 type:delete cxid:0x1a zxid:0x2a txntype:-1 reqpath:n/a Error Path:/hbase/rs/master,61500,1686791181740 Error:KeeperErrorCode = NoNode for /hbase/rs/master,61500,1686791181740
  48. 2023-06-15 09:06:30,565 INFO  [ProcessThread(sid:0 cport:2181):] server.PrepRequestProcessor: Processed session termination for sessionid: 0x188bc96d4a90000
  49. 2023-06-15 09:06:30,567 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181] server.NIOServerCnxn: Closed socket connection for client /0:0:0:0:0:0:0:1:55218 which had sessionid 0x188bc96d4a90000
  50. 2023-06-15 09:06:30,568 INFO  [M:0;master:61500] zookeeper.ZooKeeper: Session: 0x188bc96d4a90000 closed
  51. 2023-06-15 09:06:30,568 INFO  [M:0;master:61500] regionserver.HRegionServer: Exiting; stopping=master,61500,1686791181740; zookeeper connection closed.
  52. 2023-06-15 09:06:30,568 INFO  [M:0;master:61500] server.NIOServerCnxn: Closed socket connection for client /127.0.0.1:47812 which had sessionid 0x188bc96d4a90001
  53. 2023-06-15 09:06:30,568 INFO  [main-EventThread] zookeeper.ClientCnxn: EventThread shut down for session: 0x188bc96d4a90000
  54. 2023-06-15 09:06:30,568 INFO  [main-SendThread(localhost:2181)] zookeeper.ClientCnxn: Unable to read additional data from server sessionid 0x188bc96d4a90001, likely server has closed socket, closing socket connection and attempting reconnect
  55. 2023-06-15 09:06:30,569 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181] server.NIOServerCnxnFactory: NIOServerCnxn factory exited run method
  56. 2023-06-15 09:06:30,572 INFO  [M:0;master:61500] server.ZooKeeperServer: shutting down
  57. 2023-06-15 09:06:30,572 ERROR [M:0;master:61500] server.ZooKeeperServer: ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes
  58. 2023-06-15 09:06:30,572 INFO  [M:0;master:61500] server.SessionTrackerImpl: Shutting down
  59. 2023-06-15 09:06:30,572 INFO  [M:0;master:61500] server.PrepRequestProcessor: Shutting down
  60. 2023-06-15 09:06:30,572 INFO  [M:0;master:61500] server.SyncRequestProcessor: Shutting down
  61. 2023-06-15 09:06:30,572 INFO  [ProcessThread(sid:0 cport:2181):] server.PrepRequestProcessor: PrepRequestProcessor exited loop!
  62. 2023-06-15 09:06:30,572 INFO  [SyncThread:0] server.SyncRequestProcessor: SyncRequestProcessor exited!
  63. 2023-06-15 09:06:30,573 INFO  [M:0;master:61500] server.FinalRequestProcessor: shutdown of request processor complete
  64. 2023-06-15 09:06:30,574 INFO  [M:0;master:61500] zookeeper.MiniZooKeeperCluster: Shutdown MiniZK cluster with all ZK servers
复制代码
在hbase-site.xml设置文件，添加如下设置：
  1. <property>
  2.         <name>hbase.unsafe.stream.capability.enforce</name>
  3.         <value>false</value>
  4. </property>
复制代码
（三）ATLAS相干

1. ATLAS的日记在那里？
  1. /opt/rills/software/apache-atlas-2.1.0/logs/application.log
复制代码
2. 内置HIVE的日记在那里？
  1. 首先，日志日志存储在HIVE服务运行的机器上，在hive/conf/hive-log4j2.properties文件中进行了配置。
  2. 该文件如果不存在，就会使用默认存储路径，HIVE日志日志默认的存储路径是：
  3. hive.root.logger=WARN,DRFAhive.log.dir=/tmp/${user.name}/${hive.log.file}（默认的文件名为：hive.log）
复制代码
3. ATLAS启动非常慢？
  1. ATLAS在第一次启动非常慢，一般都在10分钟左右，具体时间根据主机的性能而定。
  2. 如果ATLAS命令行启动显示成功 且 HBASE正常 且 SOLR正常，
  3. 那就只能等着ATLAS完全启动完毕后，UI才可以正常访问。
复制代码
回复

使用道具 举报

返回列表

民工心事
+ 我要发帖

登录后关闭弹窗

登录参与点评抽奖  加入IT实名职场社区
去登录
快速回复 返回顶部 返回列表