About iEason8

iEason8 · ‎10-12-2020

@Karee I encountered this error message when I run sqlline.py of phoenix 4.7 against Hbase 2.0 (which is using phoenix 5.0), so please make sure you're really using phoenix 5.0 client jar. In addition, I'm upgrading Hbase from 1.2 to 2.0, then I got the same issue as your (SYSTEM.CATALOG: Didn't find expected key values for table row in metadata row) when I ran sqlline.py, do you have a idea what's the real root cause? Thanks!

iEason8 · ‎09-22-2020

@Bender , OK. Thanks for your clarification.

iEason8 · ‎09-22-2020

@Bender One more minor thing, as I mentioned before, the error message is "Service 'yarn' not found in cluster 'platform-pod10-eason-cdh'" and error number is 404 while access this API without specifying credential, which is confusing. I think it is supposed to return 401 with authentication error message. Can you help to confirm it? Thanks!

iEason8 · ‎09-17-2020

@Bender Got it. Thanks so much for your clarification.

iEason8 · ‎09-17-2020

@Bender Yes, if specifying the username and password while accessing this API via curl or wget, it can get 'clientConfig' successfully. But the specification of Cloudera Manager API said this API does not require any authentication. Ref: https://archive.cloudera.com/cm6/6.3.0/generic/jar/cm_api/apidocs/resource_ServicesResource.html#resource_ServicesResource_ClustersResourceV33_ServicesResourceV33_getClientConfig_GET There is a little background for your reference, I have a program, while it's started, it will call 'wget http://<cm_server_host>:7180/api/v13/clusters/{clusterName}/services/{serviceName}/clientConfig' directly (without specifying username/password) to get config file, and it works well with Cloudera Manager 5.10.0. After i upgraded Cloudera Manager to 6.3.0, wget will get a 404 error, then the program failed to be started.

iEason8 · ‎09-17-2020

@SibDe Sorry to disturb you. You're using Cloudera Manager 6.3.x? Could you please help me to verify a issue I encountered now? FYI. I upgraded Cloudera Manager from 5.10.0 to 6.3.0, then the following API seems not work well. Can you help to verify if 'wget http://<cm_server_host>:7180/api/v13/clusters/<cluster_name>/services/<service_name>/clientConfig' can work as expected? Thanks in advance!!

iEason8 · ‎09-16-2020

@Bender Do you (or anyone) have a Cloudera Manager 6.3.x installed? If yes, could you please help to try to run 'wget http://<cm_server_host>:7180/api/v33/clusters/{clusterName}/services/{serviceName}/clientConfig' to check if it can work as expected? Thanks a lot!

iEason8 · ‎09-15-2020

@Bender yes, the issue still exists even if i use v33 API. The strange points are: This API /clusters/{clusterName}/services/{serviceName}/clientConfig is supposed to not require any authentication, but i need to specify credential to access it succesfully via curl/wget. If i don't specify credential, the error message is "Service 'yarn' not found in cluster 'platform-pod10-eason-cdh'.", but 'yarn' is actually in the cluster, which is confusing. Is there a switch of the authentication (e.g. turn on/off)? or did i miss anything? Thanks in advance!

iEason8 · ‎09-15-2020

I upgraded Cloud Manager from 5.10.0 to 6.3.0, then i tried to run 'wget http://10.0.0.209:7180/api/v13/clusters/{clusterName}/services/{serviceName}/clientConfig', got a error 404. Checked the log file of cloudera-scm-server, got the following: 2020-09-15 04:11:57,977 INFO scm-web-16747:com.cloudera.api.ApiExceptionMapper: Exception caught in API invocation. Msg:Service 'yarn' not found in cluster 'platform-pod10-eason-cdh'. java.util.NoSuchElementException: Service 'yarn' not found in cluster 'platform-pod10-eason-cdh'. at com.cloudera.api.dao.impl.ManagerDaoBase.findService(ManagerDaoBase.java:484) ...... but I checked the services via accessing API /clusters/{clusterName}/services/{serviceName}, actually the service 'yarn' is in this cluster, ref: [root@rhel76x64 ~]# curl http://<user>:<password>@10.0.0.209:7180/api/v13/clusters/platform-pod10-eason-cdh/services/yarn/ { "healthChecks" : [ { "name" : "YARN_JOBHISTORY_HEALTH", "summary" : "GOOD", "suppressed" : false }, { "name" : "YARN_NODE_MANAGERS_HEALTHY", "summary" : "GOOD", "suppressed" : false }, { "name" : "YARN_RESOURCEMANAGERS_HEALTH", "summary" : "GOOD", "suppressed" : false }, { "name" : "YARN_USAGE_AGGREGATION_HEALTH", "summary" : "DISABLED", "suppressed" : false } ], "maintenanceOwners" : [ ], "name" : "yarn", "type" : "YARN", "clusterRef" : { "clusterName" : "cluster" }, "serviceUrl" : "http://ip-10-0-0-209.us-west-2.compute.internal:7180/cmf/serviceRedirect/yarn", "roleInstancesUrl" : "http://ip-10-0-0-209.us-west-2.compute.internal:7180/cmf/serviceRedirect/yarn/instances", "serviceState" : "STARTED", "healthSummary" : "GOOD", "configStalenessStatus" : "FRESH", "clientConfigStalenessStatus" : "FRESH", "maintenanceMode" : false, "displayName" : "YARN (MR2 Included)", "entityStatus" : "GOOD_HEALTH" In addition, i can get clientConfig successfully by running 'wget http://10.0.0.209:7180/api/v13/clusters/{clusterName}/services/{serviceName}/clientConfig --user=xxx --password=xxx --auth-no-challenge', but base on the specification of API, this API does not require any authentication. Does anyone have a clue about it? Thanks!

Online	Offline
Last Visited	‎01-10-2021 06:18 PM

Member Since	‎09-14-2020 11:50 PM
Last Visited	‎01-10-2021 06:18 PM
Posts	9

Cloudera Community

Re: Phoenix 5.0 startup error using sqlline.py wit...

Re: Failed to get clientConfig via API /clusters/{...

Re: Failed to get clientConfig via API /clusters/{...

Re: Failed to get clientConfig via API /clusters/{...

Re: Failed to get clientConfig via API /clusters/{...

Re: Using Spark Hbase Connector on CDH 6.3.2 Spark...

Re: Failed to get clientConfig via API /clusters/{...

Re: Failed to get clientConfig via API /clusters/{...

Failed to get clientConfig via API /clusters/{clus...