fang fang chen created FLUME-1195:
-------------------------------------

             Summary: flume-0.9.4: encounter "java.io.IOException: Unexpected 
exception in loadConfigs" when start flume master
                 Key: FLUME-1195
                 URL: https://issues.apache.org/jira/browse/FLUME-1195
             Project: Flume
          Issue Type: Bug
          Components: Configuration
    Affects Versions: v0.9.4
         Environment: VM, Linux
1 master node, 8 agent node
zookeeper:3 nodes
            Reporter: fang fang chen


--    I am using external zookeeper to run flume. During start flume master 
node, I got following error information in flumemaster.out. And we can find 
flume master has been started by pid files.
--    But when run "refreshAll" in flume shell, the command failed with "Could 
not increment version counter...".
--    When run flume without external zookeeper, flume can work normally. So I 
assume this is caused by zookeeper part.
       Here is the zookeeper configuration: node1 is hostname and node2/node3 
is ip.
     <property>
    <name>flume.master.zk.servers</name>
    <value>node1:2181,node2:2181,node3:2181</value>
    </property>
    </configuration>

ERROR INFORMATION:
2012-05-09 01:09:39,418 [main] ERROR master.ConfigManager: ConfigStore init 
threw IOException
java.io.IOException: Unexpected exception in loadConfigs
        at 
com.cloudera.flume.master.ZooKeeperConfigStore.loadConfigs(ZooKeeperConfigStore.java:267)
        at 
com.cloudera.flume.master.ZooKeeperConfigStore$1.success(ZooKeeperConfigStore.java:138)
        at com.cloudera.flume.master.ZKClient$1.doTry(ZKClient.java:169)
        at com.cloudera.util.RetryHarness.attempt(RetryHarness.java:64)
        at com.cloudera.flume.master.ZKClient.init(ZKClient.java:178)
        at 
com.cloudera.flume.master.ZooKeeperConfigStore.connect(ZooKeeperConfigStore.java:145)
        at 
com.cloudera.flume.master.ZooKeeperConfigStore.init(ZooKeeperConfigStore.java:110)
        at com.cloudera.flume.master.ConfigManager.start(ConfigManager.java:375)
        at 
com.cloudera.flume.master.flows.FlowConfigManager.start(FlowConfigManager.java:291)
        at 
com.cloudera.flume.master.TranslatingConfigurationManager.start(TranslatingConfigurationManager.java:391)
        at com.cloudera.flume.master.FlumeMaster.serve(FlumeMaster.java:295)
        at com.cloudera.flume.master.FlumeMaster.main(FlumeMaster.java:556)
Caused by: java.io.IOException: Not a data file.
        at 
org.apache.avro.file.DataFileStream.initialize(DataFileStream.java:105)
        at org.apache.avro.file.DataFileStream.<init>(DataFileStream.java:84)
        at 
com.cloudera.flume.master.ZooKeeperConfigStore.deserializeConfigs(ZooKeeperConfigStore.java:190)
        at 
com.cloudera.flume.master.ZooKeeperConfigStore.loadConfigs(ZooKeeperConfigStore.java:265)
        ... 11 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to