Blueprint: { "Blueprints" : { "stack_name" : "HDP", "stack_version" : "2.3" }, "configurations" : [ { "hive-site" : { "properties" : { "javax.jdo.option.ConnectionDriverName" : "com.mysql.jdbc.Driver", "javax.jdo.option.ConnectionURL" : "jdbc:mysql://%HOSTGROUP::hg_master_node_3%/hive?createDatabaseIfNotExist=true", "javax.jdo.option.ConnectionUserName": "hive" } } }, { "oozie-site" : { "properties" : { "oozie.service.JPAService.jdbc.driver" : "com.mysql.jdbc.Driver", "oozie.service.JPAService.jdbc.url" : "jdbc:mysql://%HOSTGROUP::hg_master_node_3%/oozie", "oozie.service.JPAService.jdbc.username" : "oozie", "oozie.db.schema.name" : "oozie", } } }, { "oozie-env" : { "properties" : { "oozie_hostname" : "%HOSTGROUP::hg_master_node_3%", "oozie_database" : "Existing MySQL Database" } } }, { "hive-env" : { "properties" : { "hive_database" : "Existing MySQL Database", "hive_database_name" : "hive", "hive_database_type" : "mysql", "hive_hostname" : "%HOSTGROUP::hg_master_node_3%" } } } ], "host_groups" : [ ... ] } Hostgroup-Mapping/Cluster: { "blueprint" : "bigdata_blueprint", "default_password" : "my-super-secret-password", "configurations" : [ { "hive-site" : { "properties" : { "javax.jdo.option.ConnectionPassword" : "my-super-secret-password_2" } } }, { "oozie-site" : { "properties" : { "oozie.service.JPAService.jdbc.password" : "my-super-secret-password_3" } } } ], "host_groups" :[ ... ] } ... View more

@Jeremy Dyer Solr submits all its files to HDFS with the replication factor set to 1, meaning all Solr index and data files are stored with an HDFS replication of 1. Therefore, the Solr replication should be used. I am not sure if there is a Solr configuration parameter to set the HDFS replication for Solr files. Does that help? ... View more

@pankaj singh Another option would be to get the log files directly from the individual nodes. For example, use the following request to get all the task information for a request: http://horton01.example.com:8080/api/v1/clusters/bigdata/requests/111?fields=*,tasks/Tasks/request_id,tasks/Tasks/command,tasks/Tasks/command_detail,tasks/Tasks/host_name,tasks/Tasks/id,tasks/Tasks/role,tasks/Tasks/status&minimal_response=true The response looks something like this => "tasks" : [ { "Tasks" : { "command" : "CUSTOM_COMMAND", "command_detail" : "RESTART MAPREDUCE2/MAPREDUCE2_CLIENT", "host_name" : "horton01.example.com", "id" : 1157, "request_id" : 111, "role" : "MAPREDUCE2_CLIENT", "status" : "COMPLETED" } }, { "Tasks" : { "command" : "CUSTOM_COMMAND", "command_detail" : "RESTART MAPREDUCE2/HISTORYSERVER", "host_name" : "horton02.example.com", "id" : 1158, "request_id" : 111, "role" : "HISTORYSERVER", "status" : "COMPLETED" } }, The import parts are the id and the host_name Now you can log into the host and retrieve the error and output logfile from: error: /var/lib/ambari-agent/data/errors-<id>.txt output: /var/lib/ambari-agent/data/output-<id>.txt For Example on host horton02.example.com: error log: /var/lib/ambari-agent/data/errors-1158.txt output log: /var/lib/ambari-agent/data/output-1158.txt Note: You might also be able to get the request and tasks ids from the Ambari Database. ... View more