SAP Vora 1.2 -从HANA读取Vora表
SAP Vora 1.2 -从HANA读取Vora表
提问于 2016-05-12 07:33:42
!!！更新！
最后，经过几个小时的文档研究，我发现了这个问题。结果发现，我在Yarn配置中缺少一些参数。
我就是这样做的：
- 在编辑器中打开成纱-site.xml文件，或登录到Ambari并选择Yarn>Config。找到属性“yarn.nodemager.aux-services”，并将"spark_shuffle“添加到其当前值中。新的属性名应该是"mapreduce_shuffle，spark_shuffle“。
- 添加或编辑属性"yarn.nodemanager.aux-services.spark_shuffle.class"，并将其设置为"org.apache.spark.network.yarn.YarnShuffleService".
- 在所有节点管理器主机中，将火花-纱-Shuffle.jar文件(在步骤安装星火程序集文件和依赖库中下载)从Spark复制到Hadoop类路径。通常，这个文件夹位于/usr/hdp//hadoop/lib中。
- 重新启动Yarn和节点管理器
我使用SAP Vora 1.2开发版和最新的火花控制器(HANASPARKCTRL00P5-70001262.RPM)。我用火花弹把一张桌子装进了Vora。我可以在Studio的"spark_velocity“文件夹中看到表。我可以将表加载为虚拟表。问题是，由于以下错误，无法选择或预览表中的数据：
错误: SAP DBTech JDBC: 403:内部错误:为查询"SPARK_testtable“、”a1“、”SPARK_testtable“、”a2“、”a3“从”spark_velocity“打开远程数据库的游标时出错。”testtable“”SPARK_testtable“限制200。
下面是我的hanaes-site.xml文件：
<configuration>
<!-- You can either copy the assembly jar into HDFS or to lib/external directory.
Please maintain appropriate value here-->
<property>
<name>sap.hana.es.spark.yarn.jar</name>
<value>file:///usr/sap/spark/controller/lib/external/spark-assembly-1.5.2.2.3.4.0-3485-hadoop2.7.1.2.3.4.0-3485.jar</value>
<final>true</final>
</property>
<property>
<name>sap.hana.es.server.port</name>
<value>7860</value>
<final>true</final>
</property>
<!-- Required if you are copying your files into HDFS-->
<property>
<name>sap.hana.es.lib.location</name>
<value>hdfs:///sap/hana/spark/libs/thirdparty/</value>
<final>true</final>
</property>
-->
<!--Required property if using controller for DLM scenarios-->
<!--
<property>
<name>sap.hana.es.warehouse.dir</name>
<value>/sap/hana/hanaes/warehouse</value>
<final>true</final>
</property>
-->
<property>
<name>sap.hana.es.driver.host</name>
<value>ip-10-0-0-[censored].ec2.internal</value>
<final>true</final>
</property>
<!-- Change this value to vora when connecting to Vora store -->
<property>
<name>sap.hana.hadoop.datastore</name>
<value>vora</value>
<final>true</final>
</property>
<!-- // When running against a kerberos protected cluster, please maintain appropriate values
<property>
<name>spark.yarn.keytab</name>
<value>/usr/sap/spark/controller/conf/hanaes.keytab</value>
<final>true</final>
</property>
<property>
<name>spark.yarn.principal</name>
<value>hanaes@PAL.SAP.CORP</value>
<final>true</final>
</property>
-->
<!-- To enable Secure Socket communication, please maintain appropriate values in the follwing section-->
<property>
<name>sap.hana.es.ssl.keystore</name>
<value></value>
<final>false</final>
</property>
<property>
<name>sap.hana.es.ssl.clientauth.required</name>
<value>true</value>
<final>true</final>
</property>
<property>
<name>sap.hana.es.ssl.verify.hostname</name>
<value>true</value>
<final>true</final>
</property>
<property>
<name>sap.hana.es.ssl.keystore.password</name>
<value></value>
<final>true</final>
</property>
<property>
<name>sap.hana.es.ssl.truststore</name>
<value></value>
<final>true</final>
</property>
<property>
<name>sap.hana.es.ssl.truststore.password</name>
<value></value>
<final>true</final>
</property>
<property>
<name>sap.hana.es.ssl.enabled</name>
<value>false</value>
<final>true</final>
</property>
<property>
<name>spark.executor.instances</name>
<value>10</value>
<final>true</final>
</property>
<property>
<name>spark.executor.memory</name>
<value>5g</value>
<final>true</final>
</property>
<!-- Enable the following section if you want to enable dynamic allocation-->
<!--
<property>
<name>spark.dynamicAllocation.enabled</name>
<value>true</value>
<final>true</final>
</property>
<property>
<name>spark.dynamicAllocation.minExecutors</name>
<value>10</value>
<final>true</final>
</property>
<property>
<name>spark.dynamicAllocation.maxExecutors</name>
<value>20</value>
<final>true</final>
</property>
<property>
<name>spark.shuffle.service.enabled</name>
<value>true</value>
<final>true</final>
</property>
<property>
<name>sap.hana.ar.provider</name>
<value>com.sap.hana.aws.extensions.AWSResolver</value>
<final>true</final>
</property>
<property>
<name>spark.vora.hosts</name>
<value>ip-10-0-0-[censored].ec2.internal:2022,ip-10-0-0-[censored].ec2.internal:2022,ip-10-0-0-[censored].ec2.internal:2022</value>
<final>true</final>
</property>
<property>
<name>spark.vora.zkurls</name>
<value>ip-10-0-0-[censored].ec2.internal:2181,ip-10-0-0-[censored].ec2.internal:2181,ip-10-0-0-[censored].ec2.internal:2181</value>
<final>true</final>
</property>
</configuration>ls /usr/sap/spark/控制器/lib/external/
spark-assembly-1.5.2.2.3.4.0-3485-hadoop2.7.1.2.3.4.0-3485.jar-ls /sap/hana/spark/libs/第三方
Found 4 items
-rwxrwxrwx 3 hdfs hdfs 366565 2016-05-11 13:09 /sap/hana/spark/libs/thirdparty/datanucleus-api-jdo-4.2.1.jar
-rwxrwxrwx 3 hdfs hdfs 2006182 2016-05-11 13:09 /sap/hana/spark/libs/thirdparty/datanucleus-core-4.1.2.jar
-rwxrwxrwx 3 hdfs hdfs 1863315 2016-05-11 13:09 /sap/hana/spark/libs/thirdparty/datanucleus-rdbms-4.1.2.jar
-rwxrwxrwx 3 hdfs hdfs 627814 2016-05-11 13:09 /sap/hana/spark/libs/thirdparty/joda-time-2.9.3.jarls /usr/hdp/
2.3.4.0-3485 2.3.4.7-4 currentvi /var/log/hanaes/hana_控制员。
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/sap/spark/controller/lib/spark-sap-datasources-1.2.33-assembly.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/sap/spark/controller/lib/external/spark-assembly-1.5.2.2.3.4.0-3485-hadoop2.7.1.2.3.4.0-3485.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/hdp/2.3.4.0-3485/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
16/05/12 07:02:38 INFO HanaESConfig: Loaded HANA Extended Store Configuration
Found Spark Libraries. Proceeding with Current Class Path
16/05/12 07:02:39 INFO Server: Starting Spark Controller
16/05/12 07:03:11 INFO CommandRouter: Connecting to Vora Engine
16/05/12 07:03:11 INFO CommandRouter: Initialized Router
16/05/12 07:03:11 INFO CommandRouter: Server started
16/05/12 07:03:43 INFO CommandHandler: Getting BROWSE data/user/17401406272892502037-4985062628452729323_f17e36cf-0003-0015-452e-800c700001ee
16/05/12 07:03:48 INFO CommandHandler: Getting BROWSE data/user/17401406272892502037-4985062628452729329_f17e36cf-0003-0015-452e-800c700001f4
16/05/12 07:03:48 INFO VoraClientFactory: returning a Vora catalog client of this Vora catalog server: master.i-14371789.cluster:2204
16/05/12 07:03:48 INFO CBinder: searching for compat-sap-c++.so at /opt/rh/SAP/lib64/compat-sap-c++.so
16/05/12 07:03:48 WARN CBinder: could not find compat-sap-c++.so
16/05/12 07:03:48 INFO CBinder: searching for libpam.so.0 at /lib64/libpam.so.0
16/05/12 07:03:48 INFO CBinder: loading libpam.so.0 from /lib64/libpam.so.0
16/05/12 07:03:48 INFO CBinder: loading library libprotobuf.so
16/05/12 07:03:48 INFO CBinder: loading library libprotoc.so
16/05/12 07:03:48 INFO CBinder: loading library libtbbmalloc.so
16/05/12 07:03:48 INFO CBinder: loading library libtbb.so
16/05/12 07:03:48 INFO CBinder: loading library libv2runtime.so
16/05/12 07:03:48 INFO CBinder: loading library libv2net.so
16/05/12 07:03:48 INFO CBinder: loading library libv2catalog_connector.so
16/05/12 07:03:48 INFO CatalogFactory: returning a Vora catalog client of this Vora catalog server: master.i-14371789.cluster:2204
16/05/12 07:11:56 INFO CommandHandler: Getting BROWSE data/user/17401406272892502037-4985062628452729335_f17e36cf-0003-0015-452e-800c700001fa
16/05/12 07:11:56 INFO Utils: freeing the buffer
16/05/12 07:11:56 INFO Utils: freeing the buffer
16/05/12 07:12:02 INFO Utils: freeing the buffer
16/05/12 07:12:02 WARN DefaultSource: Creating a Vora Relation that is actually persistent with a temporary statement!
16/05/12 07:12:02 WARN DefaultSource: Creating a Vora Relation that is actually persistent with a temporary statement!
16/05/12 07:12:02 INFO CatalogFactory: returning a Vora catalog client of this Vora catalog server: master.i-14371789.cluster:2204
16/05/12 07:12:02 INFO Utils: freeing the buffer
16/05/12 07:12:02 INFO DefaultSource: Creating VoraRelation testtable using an existing catalog table
16/05/12 07:12:02 INFO Utils: freeing the buffer
16/05/12 07:12:11 INFO Utils: freeing the buffer
16/05/12 07:14:15 ERROR RequestOrchestrator: Result set was not fetched by connected Client. Hence cancelled the execution
16/05/12 07:14:15 ERROR RequestOrchestrator: org.apache.spark.SparkException: Job 0 cancelled part of cancelled job group f17e36cf-0003-0015-452e-800c70000216
at org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1283)
at org.apache.spark.scheduler.DAGScheduler.handleJobCancellation(DAGScheduler.scala:1229)
at org.apache.spark.scheduler.DAGScheduler$$anonfun$handleJobGroupCancelled$1.apply$mcVI$sp(DAGScheduler.scala:681)
at org.apache.spark.scheduler.DAGScheduler$$anonfun$handleJobGroupCancelled$1.apply(DAGScheduler.scala:681)
at org.apache.spark.scheduler.DAGScheduler$$anonfun$handleJobGroupCancelled$1.apply(DAGScheduler.scala:681)
at scala.collection.mutable.HashSet.foreach(HashSet.scala:79)
at org.apache.spark.scheduler.DAGScheduler.handleJobGroupCancelled(DAGScheduler.scala:681)
at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1475)
at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1458)
at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1447)
at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48)
at org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:567)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1824)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1837)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1850)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1921)
at org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1.apply(RDD.scala:902)
at org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1.apply(RDD.scala:900)
at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:147)
at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:108)
at org.apache.spark.rdd.RDD.withScope(RDD.scala:310)
at org.apache.spark.rdd.RDD.foreachPartition(RDD.scala:900)
at com.sap.hana.spark.network.CommandHandler$$anonfun$receive$2$$anonfun$applyOrElse$7.apply(CommandRouter.scala:383)
at com.sap.hana.spark.network.CommandHandler$$anonfun$receive$2$$anonfun$applyOrElse$7.apply(CommandRouter.scala:362)
at scala.collection.immutable.List.foreach(List.scala:318)
at com.sap.hana.spark.network.CommandHandler$$anonfun$receive$2.applyOrElse(CommandRouter.scala:362)
at akka.actor.Actor$class.aroundReceive(Actor.scala:467)
at com.sap.hana.spark.network.CommandHandler.aroundReceive(CommandRouter.scala:204)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
at akka.actor.ActorCell.invoke(ActorCell.scala:487)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
at akka.dispatch.Mailbox.run(Mailbox.scala:220)
at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)同样奇怪的是，这个错误：
16/05/12 07:03:48 INFO CBinder: searching for compat-sap-c++.so at /opt/rh/SAP/lib64/compat-sap-c++.so
16/05/12 07:03:48 WARN CBinder: could not find compat-sap-c++.so因为我的位置有这个文件：
ls /opt/rh/SAP/lib64 64/
compat-sap-c++.so现在将com.sap.hana.aws.extensions.AWSResolver转换为com.sap.hana.spark.aws.extensions.AWSResolver之后，日志文件看起来就不一样了：
16/05/17 10:04:08 INFO CommandHandler: Getting BROWSE data/user/9110494231822270485-5373255807276155190_7e6efa3c-0003-0015-4a91-a3b020000139
16/05/17 10:04:13 INFO CommandHandler: Getting BROWSE data/user/9110494231822270485-5373255807276155196_7e6efa3c-0003-0015-4a91-a3b02000013f
16/05/17 10:04:13 INFO Utils: freeing the buffer
16/05/17 10:04:13 INFO Utils: freeing the buffer
16/05/17 10:04:13 INFO Utils: freeing the buffer
16/05/17 10:04:13 INFO Utils: freeing the buffer
16/05/17 10:04:29 INFO Utils: freeing the buffer
16/05/17 10:04:29 WARN DefaultSource: Creating a Vora Relation that is actually persistent with a temporary statement!
16/05/17 10:04:29 WARN DefaultSource: Creating a Vora Relation that is actually persistent with a temporary statement!
16/05/17 10:04:29 INFO Utils: freeing the buffer
16/05/17 10:04:29 INFO DefaultSource: Creating VoraRelation testtable using an existing catalog table
16/05/17 10:04:29 INFO Utils: freeing the buffer
16/05/17 10:04:29 INFO Utils: freeing the buffer
16/05/17 10:04:29 INFO Utils: freeing the buffer
16/05/17 10:04:29 INFO ConfigurableHostMapper: Load Strategy: RELAXEDLOCAL (default)
16/05/17 10:04:29 INFO HdfsBlockRetriever: Length of HDFS file (/user/vora/test.csv): 10 bytes.
16/05/17 10:04:29 INFO Utils: freeing the buffer
16/05/17 10:04:29 INFO ConfigurableHostMapper: Load Strategy: RELAXEDLOCAL (default)
16/05/17 10:04:29 INFO TableLoader: Loading table [testtable]
16/05/17 10:04:29 INFO ConfigurableHostMapper: Load Strategy: RELAXEDLOCAL (default)
16/05/17 10:04:29 INFO TableLoader: Initialized 1 loading threads. Waiting until finished... -- 0.00 s
16/05/17 10:04:29 INFO TableLoader: [secondary2.i-a5361638.cluster:2202] Host mapping (Ranges: 1/1 Size: 0.00 MB)
16/05/17 10:04:29 INFO VoraJdbcClient: [secondary2.i-a5361638.cluster:2202] MultiLoad: MULTIFILE
16/05/17 10:04:29 INFO TableLoader: [secondary2.i-a5361638.cluster:2202] Host finished:
Raw ranges: 1/1
Size: 0.00 MB
Time: 0.29 s
Throughput: 0.00 MB/s
16/05/17 10:04:29 INFO TableLoader: Finished 1 loading threads. -- 0.29 s
16/05/17 10:04:29 INFO TableLoader: Updated catalog -- 0.01 s
16/05/17 10:04:29 INFO TableLoader: Table load statistics:
Name: testtable
Size: 0.00 MB
Hosts: 1
Time: 0.30 s
Cluster throughput: 0.00 MB/s
Avg throughput per host: 0.00 MB/s
16/05/17 10:04:29 INFO Utils: freeing the buffer
16/05/17 10:04:29 INFO TableLoader: Loaded table [testtable] -- 0.37 s
16/05/17 10:04:38 INFO Utils: freeing the buffer
16/05/17 10:06:43 ERROR RequestOrchestrator: Result set was not fetched by connected Client. Hence cancelled the execution
16/05/17 10:06:43 ERROR RequestOrchestrator: org.apache.spark.SparkException: Job 1 cancelled part of cancelled job group 7e6efa3c-0003-0015-4a91-a3b02000015b
at org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1283)
at org.apache.spark.scheduler.DAGScheduler.handleJobCancellation(DAGScheduler.scala:1229)
at org.apache.spark.scheduler.DAGScheduler$$anonfun$handleJobGroupCancelled$1.apply$mcVI$sp(DAGScheduler.scala:681)
at org.apache.spark.scheduler.DAGScheduler$$anonfun$handleJobGroupCancelled$1.apply(DAGScheduler.scala:681)
at org.apache.spark.scheduler.DAGScheduler$$anonfun$handleJobGroupCancelled$1.apply(DAGScheduler.scala:681)
at scala.collection.mutable.HashSet.foreach(HashSet.scala:79)
at org.apache.spark.scheduler.DAGScheduler.handleJobGroupCancelled(DAGScheduler.scala:681)
at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1475)
at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1458)
at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1447)
at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48)
at org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:567)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1824)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1837)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1850)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1921)
at org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1.apply(RDD.scala:902)
at org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1.apply(RDD.scala:900)
at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:147)
at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:108)
at org.apache.spark.rdd.RDD.withScope(RDD.scala:310)
at org.apache.spark.rdd.RDD.foreachPartition(RDD.scala:900)
at com.sap.hana.spark.network.CommandHandler$$anonfun$receive$2$$anonfun$applyOrElse$7.apply(CommandRouter.scala:383)
at com.sap.hana.spark.network.CommandHandler$$anonfun$receive$2$$anonfun$applyOrElse$7.apply(CommandRouter.scala:362)
at scala.collection.immutable.List.foreach(List.scala:318)
at com.sap.hana.spark.network.CommandHandler$$anonfun$receive$2.applyOrElse(CommandRouter.scala:362)
at akka.actor.Actor$class.aroundReceive(Actor.scala:467)
at com.sap.hana.spark.network.CommandHandler.aroundReceive(CommandRouter.scala:204)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
at akka.actor.ActorCell.invoke(ActorCell.scala:487)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
at akka.dispatch.Mailbox.run(Mailbox.scala:220)
at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)我仍然“没有被客户端取走”，但现在看来，vora加载了这个表。
有人，有什么想法怎么解决吗？当我试图读取Vora中的Hive表时，也会出现同样的错误。
错误: SAP DBTech JDBC: 403:内部错误:为查询"vora_conn_testtable“、”a1“、”vora_conn_testtable“、”a2“、”a3“从”spark_velocity“打开远程数据库的游标时出错。”testtable“”vora_conn_testtable“限制200。
回答 4
Stack Overflow用户
回答已采纳
发布于 2016-07-19 09:51:09
最后，经过几个小时的文档研究，我发现了这个问题。结果，我在Yarn配置中缺少一些参数(不知道为什么这会影响HANA连接)。
我就是这样做的：
在编辑器中打开成纱-site.xml文件，或登录到Ambari并选择Yarn>Config。找到属性“yarn.nodemager.aux-services”，并将"spark_shuffle“添加到其当前值中。新的属性名应该是"mapreduce_shuffle，spark_shuffle“。添加或编辑属性"yarn.nodemanager.aux-services.spark_shuffle.class"，并将其设置为"org.apache.spark.network.yarn.YarnShuffleService".在所有节点管理器主机中，将火花纱线-Shuffle.jar文件从Spark复制到Hadoop类路径。通常，这个文件夹位于/usr/hdp//hadoop/lib中。重新启动Yarn和节点管理器
Stack Overflow用户
发布于 2016-05-20 12:58:28
我也面临过同样的问题，现在就解决了！其原因是HANA无法理解工作节点的主机名。火花控制器发送HANA工作节点名称，其中有火花RDD。如果HANA不理解它们的主机名，HANA将无法获得结果并发生错误。
请检查HANA上的主机文件。
Stack Overflow用户
发布于 2016-05-16 20:01:52
日志显示错误Result set was not fetched by connected Client. Hence cancelled the execution。此上下文中的客户端是HANA试图从Vora获取的。
该错误可能是由HANA和Vora之间的连接问题引起的。
- The显示
sap.hana.ar.provider=com.sap.hana.aws.extensions.AWSResolver。这看上去像个打字错误。假设您在部署aws.resolver-1.5.8.jar之后使用了lib目录中包含的HANASPARKCTRL00P_5-70001262.RPM，那么正确的路径应该是com.sap.hana.spark.aws.extensions.AWSResolver。见附于SAP 2273047 - SAP火花控制器SPS 11 (与Spark 1.5.2兼容)的PDF文件 - 确保所需端口处于打开状态:参见HANA行政指南 -> 9.2.3.3火花放电控制器配置参数->端口56000-58000在所有火花执行器节点上
如果问题仍然存在，您可以检查日志中的问题：
- 启动火花控制器并复制问题/错误。
- 导航到http://:8088上的Yarn -> UI (Ambari通过Ambari -> Yarn ->快速链接->资源管理器UI提供快速链接)
- 在Yarn ResourceManager UI中，单击正在运行的Spark应用程序的列“跟踪UI”中的“ApplicationMaster”链接
- 在Spark上，单击选项卡'Executors‘。然后，对于每个执行者，单击“stdout”和“stderr”并检查错误。
无关:这些参数在Vora1.2中被废弃，您可以从hanaes-site.xml: spark.vora.hosts，spark.vora.zkurls中删除它们
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/37180192
复制相关文章
相似问题
腾讯云开发者
Copyright © 2013 - 2026 Tencent Cloud. All Rights Reserved. 腾讯云 版权所有
深圳市腾讯计算机系统有限公司 ICP备案/许可证号：粤B2-20090059 
粤公网安备44030502008569号
腾讯云计算（北京）有限责任公司 京ICP证150476号 | 京ICP备11018762号