Hello @quangbilly79    Thanks for using Cloudera Community. The "Spark Master" refers to the Resource Manager responsible for allocating resources. Since you are using YARN, Your Team needs to use "--master yarn". The usage of "--master spark://<IP Address>:7077" is for Spark Standalone Cluster, which isn't the Case for your team.   To your Observation concerning the "Driver Instance" & "Worker Instance" being added via "Add Role Instance", there is no such Option as YARN is the Resource Manager, which shall allocate the resources for Spark Driver & Executors.   Review [1] for the usage of "--master" as well. Hope the above answers your Team's queries.   Regards, Smarak   [1] https://spark.apache.org/docs/latest/submitting-applications.html#launching-applications-with-spark-submit ... View more

Hello @ighack    Thanks for using Cloudera Community. In such Cases, Kindly review the StdOut & StdErr within the Directory shared in the 1st line of the Screenshot (Ending with "8464-hbase-MASTER"). These 2 files would offer additional details into the JVM StartUp. Note that Role Log would be Useful, if the Role was terminated by any issues specific to HBase while the StdOut & StdErr are Useful wherein OS/JVM concerns cause the Role StartUp issues.   Regards, Smarak ... View more

Hello @Menyawy    Thanks for using Cloudera Community. The Error [1] indicates your Team is using CDH v5.x using HBase v1.x. In the concerned release, We have limited choices to ensure "hbase:namespace" Table Region is assigned correctly as shared below:   (I) Easier Yet Not-Always-Successful Option: 1) Shutdown HBase Service 2) echo "rmr /hbase" | hbase zkcli (From HMaster Node) 3) Start HBase Service 4) sudo hbase hbase hbck -fixAssignments (II) Review whether any of the "hbase:namespace" Table Region files are reporting MissingBlockException. If Yes, We need to fix the MissingBlockException. (III) Possible for the RegionServer Logs (Wherein the "hbase:namespace" Table Region is being assigned) would offer additional insight into the reasoning for the RegionServer being Unable to assign the "hbase:namespace" Table Region successfully. Your Team may review the concerned RegionServer Logs as well.   There may be Other Options, yet such Inconsistencies are better handled in HBase 2.x [1] & your Team should plan for using HBase v2.x soon.   Regards, Smarak   [1] https://github.com/apache/hbase-operator-tools/blob/master/hbase-hbck2/README.md#master-startup-cannot-progress-in-holding-pattern-until-region-onlined ... View more

Hello @bgkim    Thanks for using Cloudera Community. To your Q, the Composite Primary Key would require using both A & B in WHERE Clause as the Indexing is done collectively. As such, Your SELECT Query would ideally benefit upon creating a Local Index on A & C. You may review [1] as Read-Heavy Use-Case benefit via Global Index with Penalty incurred during Writes. Additionally, Phoenix offers Covered Index & Explain Plan helps confirming the Index Usage. Link [2] offers few examples as well.    With all recommendations, Best Advise is always to review the Performance internally prior to implementing them in Production.    Regards, Smarak   [1] https://phoenix.apache.org/secondary_indexing.html  [2] https://learn.microsoft.com/en-us/azure/hdinsight/hbase/apache-hbase-phoenix-performance  ... View more

I agree with Smarak, the error code typically means that there were not enough resources available to start the job. You could probably use Grafana dashboard (available in the Admin page) to look at the cluster resources and load around the time you had this issue. Is it happening consistently?   For Jobs, I usually see this at the start or end of the month, when a lot of people schedule periodic jobs and they all trigger at the same time. ... View more

Hello @Girija    Since we haven't heard back from you, We shall mark the Post as Solved. If you happen to have any further ask, Feel free to Update the Post. In Summary, Internally, I wasn't able to replicate the issue being faced by you as I was able to create the ConfigSet using "_default" ConfigSet as baseConfig.  Customer can use the below solrctl command to create a ConfigSet with Solr KeyTab: solrctl config --create Test_Config _default -p configSetProp.immutable=false Assuming the above Command fails, Running the solrctl command with "--trace" after "solrctl" & before "config" would print the trace logging & assist in troubleshooting the issue faced by your team.    Regards, Smarak ... View more