@raghavendra v Ambari Blueprints are used to create clusters based on the Blueprint template. Using blueprint we can not make configuration changes to an existing cluster. It means if you have the Production Cluster Blueprint (exported blueprint) then using that blueprint (cluster configuration) you can create new clusters, However you can not make cluster configuration changes using blueprint. Ambari Blueprints are a declarative definition of a cluster. With a Blueprint, you specify aStack, the Component layout and the Configurations to materialize a Hadoop cluster instance (via a REST API) without having to use the Ambari Cluster Install Wizard. https://cwiki.apache.org/confluence/display/AMBARI/Blueprints ... View more

@Sami Ahmad I made some changes to your code, it should look like following to work properly: import java.io.IOException; import org.apache.hadoop.hbase.util.Bytes; import org.apache.hadoop.hbase.client.HBaseAdmin; import org.apache.hadoop.hbase.HBaseConfiguration; import org.apache.hadoop.hbase.HColumnDescriptor; import org.apache.hadoop.hbase.HTableDescriptor; import org.apache.hadoop.hbase.client.Admin; import org.apache.hadoop.hbase.client.Connection; import org.apache.hadoop.hbase.client.ConnectionFactory; import org.apache.hadoop.hbase.TableName; import org.apache.hadoop.conf.Configuration; public class CreateHbaseTable { public void createtable(String name, String[] colfamily)throws Exception { Configuration config = HBaseConfiguration.create(); config.set("hbase.zookeeper.quorum", "hadoop1,hadoop2"); config.set("hbase.zookeeper.property.clientPort", "2181"); config.set("hbase.cluster.distributed", "true"); config.set("zookeeper.znode.parent", "/hbase-unsecure"); HBaseAdmin admin = new HBaseAdmin(config); HTableDescriptor des = new HTableDescriptor(Bytes.toBytes(name)); for (int i = 0; i < colfamily.length; i++) { des.addFamily(new HColumnDescriptor(colfamily[i])); } if (admin.tableExists(name)) { System.out.println("Table already exist"); } else { admin.createTable(des); System.out.println("Table: " + name + " Sucessfully created"); } } public static void main(String args[]) throws Exception { CreateHbaseTable op = new CreateHbaseTable(); String tablename = "Acadgild"; String[] familys = { "Emp_name", "sal" }; op.createtable(tablename, familys); } } . Now in order to compile and run this code please do this: # export CLASSPATH=`hbase classpath`:. # javac CreateHbaseTable.java # java CreateHbaseTable OUTPUT: . . 2018-06-09 00:40:18,504 INFO [main] client.HBaseAdmin: Created Acadgild Table: Acadgild Sucessfully created . Additionally if you want to use Maven Based Simple HBase client then please refer to: https://github.com/jaysensharma/MiddlewareMagicDemos/tree/master/HDP_Ambari/HBase/HBase_Client ... View more

@Michael Bronson When we want to do GC log rotation then in that case we will have to define few properties together to make it work appropriately like following along with the "-Xloggc" option. -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M Just defining NumberOfGClogFiles option will lead to inconsistent JVM options and JVM will not boot like: So please try this: HBASE_MASTER_OPTS=" -XX:PermSize=64m -XX:MaxPermSize={{hbase_master_maxperm_size}} -Xms{{hbase_heapsize}} -Xmx{{hbase_heapsize}} -Xmn{{hbase_master_xmn_size}} -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseCMSInitiatingOccupancyOnly -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=3 -XX:GCLogFileSize=20M" . NOTE: Also in your case the JVM was not booting because there is a Typo in your case "-XX:NumberOfGClogFiles" (here you used lowercase log) where as the correct option has Uppercase L in the option like "-XX:NumberOfGCLogFiles" ... View more

@Michael Bronson The Logs (like collector-gc.log Or gc.log) produced by the JVM following are not controlled by the Log4j So there is no way to control them or their rotations using Log4j -Xloggc:/var/log/ambari-metrics-collector/collector-gc.log-201806070708 -Xloggc:/var/log/ambari-metrics-collector/gc.log-201806070708 In order to control those GC log files you will need to rely on the OS utilities like "logrotate" or "cronjobs" to clear those logs. . JVM provides some options like "-XX:+UseGCLogFileRotation" however they are responsible for rotating the GC logs when the JVM process is keep running. However You can however control the AMS component logs like HMaster logs or AMS collector logs using the log4j settings like: log4j.appender.file.MaxFileSize={{ams_log_max_backup_size}}MB log4j.appender.file.MaxBackupIndex={{ams_log_number_of_backup_files}} . ... View more