You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Andrew Onischuk <ao...@hortonworks.com> on 2015/11/18 08:37:18 UTC

Review Request 40430: Kafka can not to start with custom lo/pid dirs with changed permissions after ambari-server reset

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40430/
-----------------------------------------------------------

Review request for Ambari and Vitalyi Brodetskyi.


Bugs: AMBARI-13935
    https://issues.apache.org/jira/browse/AMBARI-13935


Repository: ambari


Description
-------

Steps:

  1. Before deploy were created log and PID dirs with root owners, root group and 000 permissions.
  2. Deployed cluster via UI.

Result: Kafka's check was failed:

    
    
    
    stderr: 
    Traceback (most recent call last):
      File "/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/service_check.py", line 60, in <module>
        ServiceCheck().execute()
      File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 218, in execute
        method(env)
      File "/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/service_check.py", line 43, in service_check
        call_and_match_output(command, format("({create_topic_cmd_created_output})|({create_topic_cmd_exists_output})"), "Failed to check that topic exists", user=params.kafka_user)
      File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py", line 55, in wrapper
        return function(*args, **kwargs)
      File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/validate.py", line 36, in call_and_match_output
        raise Fail(err_message)
    resource_management.core.exceptions.Fail: Failed to check that topic exists
     stdout:
    2015-11-16 11:45:22,087 - Running kafka create topic command: source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1
    2015-11-16 11:45:22,087 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:23,186] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:23,515 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:23,186] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    2015-11-16 11:45:23,517 - Will retry 9 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
    2015-11-16 11:45:25,520 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:26,690] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:27,017 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:26,690] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    2015-11-16 11:45:27,018 - Will retry 8 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
    2015-11-16 11:45:29,020 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:30,190] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:30,516 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:30,190] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    2015-11-16 11:45:30,517 - Will retry 7 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
    2015-11-16 11:45:32,519 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:33,705] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:34,030 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:33,705] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    2015-11-16 11:45:34,031 - Will retry 6 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
    2015-11-16 11:45:36,033 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:37,277] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:37,603 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:37,277] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    2015-11-16 11:45:37,604 - Will retry 5 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
    2015-11-16 11:45:39,606 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:40,824] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:41,151 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:40,824] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    2015-11-16 11:45:41,152 - Will retry 4 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
    2015-11-16 11:45:43,154 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:44,218] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:44,545 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:44,218] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    2015-11-16 11:45:44,546 - Will retry 3 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
    2015-11-16 11:45:46,548 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:47,675] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:48,003 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:47,675] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    2015-11-16 11:45:48,003 - Will retry 2 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
    2015-11-16 11:45:50,004 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:51,132] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:51,460 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:51,132] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    2015-11-16 11:45:51,460 - Will retry 1 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
    2015-11-16 11:45:53,463 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
    WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
    Error while executing topic command : replication factor: 1 larger than available brokers: 0
    [2015-11-16 11:45:54,546] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
    	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
    	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
    	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
    	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
    	at kafka.admin.TopicCommand.main(TopicCommand.scala)
     (kafka.admin.TopicCommand$)
    2015-11-16 11:45:54,872 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:54,546] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
    

cluster: <http://172.22.110.91:8080/>, lifetime: +120h.


Diffs
-----

  ambari-agent/src/main/python/ambari_agent/HostInfo.py 4082ebe 
  ambari-agent/src/test/python/ambari_agent/TestHostInfo.py 9a9dcb2 

Diff: https://reviews.apache.org/r/40430/diff/


Testing
-------

mvn clean test


Thanks,

Andrew Onischuk


Re: Review Request 40430: Kafka can not to start with custom lo/pid dirs with changed permissions after ambari-server reset

Posted by Vitalyi Brodetskyi <vb...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40430/#review106995
-----------------------------------------------------------

Ship it!


Ship It!

- Vitalyi Brodetskyi


On Лис. 18, 2015, 7:37 до полудня, Andrew Onischuk wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40430/
> -----------------------------------------------------------
> 
> (Updated Лис. 18, 2015, 7:37 до полудня)
> 
> 
> Review request for Ambari and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-13935
>     https://issues.apache.org/jira/browse/AMBARI-13935
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Steps:
> 
>   1. Before deploy were created log and PID dirs with root owners, root group and 000 permissions.
>   2. Deployed cluster via UI.
> 
> Result: Kafka's check was failed:
> 
>     
>     
>     
>     stderr: 
>     Traceback (most recent call last):
>       File "/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/service_check.py", line 60, in <module>
>         ServiceCheck().execute()
>       File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 218, in execute
>         method(env)
>       File "/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/service_check.py", line 43, in service_check
>         call_and_match_output(command, format("({create_topic_cmd_created_output})|({create_topic_cmd_exists_output})"), "Failed to check that topic exists", user=params.kafka_user)
>       File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/decorator.py", line 55, in wrapper
>         return function(*args, **kwargs)
>       File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/validate.py", line 36, in call_and_match_output
>         raise Fail(err_message)
>     resource_management.core.exceptions.Fail: Failed to check that topic exists
>      stdout:
>     2015-11-16 11:45:22,087 - Running kafka create topic command: source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1
>     2015-11-16 11:45:22,087 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:23,186] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:23,515 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:23,186] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     2015-11-16 11:45:23,517 - Will retry 9 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
>     2015-11-16 11:45:25,520 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:26,690] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:27,017 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:26,690] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     2015-11-16 11:45:27,018 - Will retry 8 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
>     2015-11-16 11:45:29,020 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:30,190] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:30,516 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:30,190] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     2015-11-16 11:45:30,517 - Will retry 7 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
>     2015-11-16 11:45:32,519 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:33,705] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:34,030 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:33,705] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     2015-11-16 11:45:34,031 - Will retry 6 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
>     2015-11-16 11:45:36,033 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:37,277] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:37,603 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:37,277] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     2015-11-16 11:45:37,604 - Will retry 5 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
>     2015-11-16 11:45:39,606 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:40,824] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:41,151 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:40,824] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     2015-11-16 11:45:41,152 - Will retry 4 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
>     2015-11-16 11:45:43,154 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:44,218] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:44,545 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:44,218] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     2015-11-16 11:45:44,546 - Will retry 3 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
>     2015-11-16 11:45:46,548 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:47,675] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:48,003 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:47,675] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     2015-11-16 11:45:48,003 - Will retry 2 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
>     2015-11-16 11:45:50,004 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:51,132] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:51,460 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:51,132] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     2015-11-16 11:45:51,460 - Will retry 1 time(s), caught exception: Failed to check that topic exists. Sleeping for 2 sec(s)
>     2015-11-16 11:45:53,463 - call['source /usr/hdp/current/kafka-broker/config/kafka-env.sh ; /usr/hdp/current/kafka-broker//bin/kafka-topics.sh --zookeeper ambari-us-rhe6-logpid-13b-3.novalocal:2181,ambari-us-rhe6-logpid-13b-5.novalocal:2181,ambari-us-rhe6-logpid-13b-4.novalocal:2181 --create --topic ambari_kafka_service_check --partitions 1 --replication-factor 1'] {'logoutput': True, 'user': 'cstm-kafka', 'quiet': False}
>     WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
>     Error while executing topic command : replication factor: 1 larger than available brokers: 0
>     [2015-11-16 11:45:54,546] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0
>     	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)
>     	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)
>     	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)
>     	at kafka.admin.TopicCommand$.main(TopicCommand.scala:60)
>     	at kafka.admin.TopicCommand.main(TopicCommand.scala)
>      (kafka.admin.TopicCommand$)
>     2015-11-16 11:45:54,872 - call returned (1, "WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.\nError while executing topic command : replication factor: 1 larger than available brokers: 0\n[2015-11-16 11:45:54,546] ERROR kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers: 0\n\tat kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:77)\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:236)\n\tat kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:105)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:60)\n\tat kafka.admin.TopicCommand.main(TopicCommand.scala)\n (kafka.admin.TopicCommand$)")
>     
> 
> cluster: <http://172.22.110.91:8080/>, lifetime: +120h.
> 
> 
> Diffs
> -----
> 
>   ambari-agent/src/main/python/ambari_agent/HostInfo.py 4082ebe 
>   ambari-agent/src/test/python/ambari_agent/TestHostInfo.py 9a9dcb2 
> 
> Diff: https://reviews.apache.org/r/40430/diff/
> 
> 
> Testing
> -------
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>