我正在尝试使用wso2-das服务器连接到HBase .
我需要从wso2DAS连接到Hbase，我按照所有步骤从下面的链接进行设置 . WSO2DAS没有连接到Hbase.Master和区域服务器，都运行正常 . 但继续得到“无法得到位置错误”
https://docs.wso2.com/pages/viewpage.action?pageId=45952699
主服务器和区域服务器都运行良好 . 还在
[2016-10-23 16：15：11,477]错误 - 创建表时出错或设置表的模式：test_2 org.wso2.carbon.analytics.datasource . commons.exception.AnalyticsException：检查租户-1234的表TEST_2是否存在时出错：无法在org.wso2的org.wso2.carbon.analytics.datasource.hbase.HBaseAnalyticsRecordStore.tableExists（HBaseAnalyticsRecordStore.java:140）中获取位置位于org.wso2.carbon.analytics的org.wso2.carbon.analytics.dataservice.core.AnalyticsDataServiceImpl.createTableFinal（AnalyticsDataServiceImpl.java:401）中的.carbon.analytics.datasource.hbase.HBaseAnalyticsRecordStore.createTable（HBaseAnalyticsRecordStore.java:99）位于org.wso2.carbon.analytics.eventsink.AnalyticsEventStoreDeployer.addEventStore的org.wso2.carbon.analytics.api.CarbonAnalyticsAPI.createTable（CarbonAnalyticsAPI.java:134）中的.dataservice.core.AnalyticsDataServiceImpl.createTable（AnalyticsDataServiceImpl.java:378） （AnalyticsEventSt oreDeployer.java:108）org.wso2.carbon.analytics.eventsink.AnalyticsEventStoreDeployer.deploy（AnalyticsEventStoreDeployer.java:78）at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy（DeploymentFileData.java:136） org.apache.axis2.deployment.DeploymentEngine.doDeploy（DeploymentEngine.java:807）org.apache.axis.deployment.repository.util.WSInfoList.update（WSInfoList.java:144）org.apache.axis2.deployment .rpositoryListener.update（RepositoryListener.java:377）位于org.apache.axis2.deployment.RepositoryListener.checkServices（RepositoryListener.java:254）org.apache.axis2.deployment.RepositoryListener.startListener（RepositoryListener.java:371）at at Org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository（SchedulerTask.java:59）位于org.wso2.carbon.core的org.apache.axis2.deployment.scheduler.SchedulerTask.run（SchedulerTask.java:67） . 在org.wso2.carbon.core.d上部署.CarbonDeploymentSchedulerTask.runAxisDeployment（CarbonDeploymentSchedulerTask.java:93） java.util.concurrent.Executors中的eployment.CarbonDeploymentSchedulerTask.run（CarbonDeploymentSchedulerTask.java:138）java上的java.util.concurrent.FutureTask.runAndReset（FutureTask.java：308）中的$ RunnableAdapter.call（Executors.java:511） .util.concurrent.ScheduledThreadPoolExecutor $ ScheduledFutureTask.access $ 301（ScheduledThreadPoolExecutor.java:180）java.util.concurrent.ScheduledThreadPoolExecutor $ ScheduledFutureTask.run（ScheduledThreadPoolExecutor.java:294）at java.util.concurrent.ThreadPoolExecutor.runWorker（ThreadPoolExecutor . java：1142）at java.util.concurrent.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:617）at java.lang.Thread.run（Thread.java:745）引起：org.apache.hadoop.hbase.client .RetriesExhaustedException：无法在org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call（ScannerCallableWithReplicas.java:156）的org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations（RpcRetryingCallerWithReadReplicas.java:319）中获取位置 . ） 在org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call（ScannerCallableWithReplicas.java:60）位于org.apache.hadoop.hbase的org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries（RpcRetryingCaller.java:200） . 客户端.ClientScanner.call（ClientScanner.java:326）位于org.apache.hadoop.hbase.client.ClientScanner.nextScanner（ClientScanner.java:301）org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction（ClientScanner . java：166）在org.apache的org.apache.hadoop.hbase.client.ClientScanner . （ClientScanner.java:161）org.apache.hadoop.hbase.client.HTable.getScanner（HTable.java:794） . hadoop.hbase.MetaTableAccessor.fullScan（MetaTableAccessor.java:602）org.apache.hadoop.hbase.MetaTableAccessor.tableExists（MetaTableAccessor.java:366）org.apache.hadoop.hbase.client.HBaseAdmin.tableExists（HBaseAdmin . java：403）at org.wso2.carbon.analytics.datasource.hbase.HBaseAnalyticsRecordStore.tableExists（HBaseAnalyticsRecordStore.java:137）... 23更多[2016-10-23 16： 15：11,481]错误 - 为租户ID部署文件：test_2.xml时出错：-1234 org.wso2.carbon.analytics.eventsink.exception.AnalyticsEventStoreException：创建表时出错或设置表的架构：test.org at org.wso2.carbon.analytics.eventsink.AnalyticsEventStoreDeployer.addEventStore（AnalyticsEventStoreDeployer.java:125）org.wso2.carbon.analytics.eventsink.AnalyticsEventStoreDeployer.deploy（AnalyticsEventStoreDeployer.java:78）at org . 位于org.apache.axis2.deployment.repository的org.apache.axis2.deployment.DeploymentEngine.doDeploy（DeploymentEngine.java:807）上的apache.axis2.deployment.repository.util.DeploymentFileData.deploy（DeploymentFileData.java:136） . util.WSInfoList.update（WSInfoList.java:144）org.apache.axis2.deployment.RepositoryListener.update（RepositoryListener.java:377）at org.apache.axis2.deployment.RepositoryListener.checkServices（RepositoryListener.java:254）在org.apache.axis2.deployment.RepositoryLis tener.startListener（RepositoryListener.java:371）org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository（SchedulerTask.java:59）at org.apache.axis2.deployment.scheduler.SchedulerTask.run（SchedulerTask.java： 67）atg.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment（CarbonDeploymentSchedulerTask.java:93）at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run（CarbonDeploymentSchedulerTask.java:138）at java.util.concurrent .Executors $ RunnableAdapter.call（Executors.java:511）at java.util.concurrent.FutureTask.runAndReset（FutureTask.java:308）at java.util.concurrent.ScheduledThreadPoolExecutor $ ScheduledFutureTask.access $ 301（ScheduledThreadPoolExecutor.java:180） at java.util.concurrent.ScheduledThreadPoolExecutor $ ScheduledFutureTask.run（ScheduledThreadPoolExecutor.java:294）at java.util.concurrent.ThreadPoolExecutor.runWorker（ThreadPoolExecutor.java:1142）at java.util.concurrent.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor）的.java：617） at java.lang.Thread.run（Thread.java:745）引起：org.wso2.carbon.analytics.datasource.co