Ok first I apologize for not having the serve-properties attached last night. You will find it attached to this email.
Second I was trying with putty before to check the connection. It was working with raw data but you're right it's not working with a telnet. I have already opened kafka and zookeeper ports on the windows client side, where the consumer runs. the producer runs btw in my ubuntu vm. Thanks, Andre On Wed, Feb 20, 2013 at 8:43 PM, Neha Narkhede <neha.narkh...@gmail.com>wrote: > It doesn't seem like your consumer box has access to the zookeeper box. > Have you tried telnetting to the zookeeper host/port ? I suspect that will > fail as well. > > Thanks, > Neha > > > On Wed, Feb 20, 2013 at 7:48 PM, Andre Z <a.zierfuss....@gmail.com> wrote: > > > It might be related but my changes didn't do anything. > > > > I have the server-properties attached. > > > > Here is my timeout error: > > Exception in thread "main" > > org.I0Itec.zkclient.exception.ZkTimeoutException: Unable to connect to > > zookeeper server within timeout: 4000 > > at org.I0Itec.zkclient.ZkClient.connect(ZkClient.java:876) > > at org.I0Itec.zkclient.ZkClient.<init>(ZkClient.java:98) > > at org.I0Itec.zkclient.ZkClient.<init>(ZkClient.java:84) > > at > > > > > kafka.consumer.ZookeeperConsumerConnector.connectZk(ZookeeperConsumerConnector.scala:152) > > at > > > > > kafka.consumer.ZookeeperConsumerConnector.<init>(ZookeeperConsumerConnector.scala:122) > > at > > > > > kafka.javaapi.consumer.ZookeeperConsumerConnector.<init>(ZookeeperConsumerConnector.scala:65) > > at > > > > > kafka.javaapi.consumer.ZookeeperConsumerConnector.<init>(ZookeeperConsumerConnector.scala:67) > > at > > > > > kafka.consumer.Consumer$.createJavaConsumerConnector(ConsumerConnector.scala:88) > > at > > > > > kafka.consumer.Consumer.createJavaConsumerConnector(ConsumerConnector.scala) > > at consumer1.Consumer.<init>(Consumer.java:51) > > at consumer1.NewConsumer.main(NewConsumer.java:16) > > > > > > And also the: > > [2013-02-20 19:41:13,196] INFO Accepted socket connection from / > > 192.168.190.188:49652 (org.apache.zookeeper.server.NIOServerCnxn) > > [2013-02-20 19:41:13,197] WARN EndOfStreamException: Unable to read > > additional data from client sessionid 0x0, likely client has closed > socket > > (org.apache.zookeeper.server.NIOServerCnxn) > > [2013-02-20 19:41:13,197] INFO Closed socket connection for client / > > 192.168.190.188:49652 (no session established for client) > > (org.apache.zookeeper.server.NIOServerCnxn) > > > > I hope this helps to find the problem. > > > > Thx, > > Andre > > > > On Tue, Feb 19, 2013 at 9:14 PM, Jun Rao <jun...@gmail.com> wrote: > > > > > Is this related to item #2 in http://kafka.apache.org/faq.html ? > > > > > > Thanks, > > > > > > Jun > > > > > > On Tue, Feb 19, 2013 at 5:32 PM, Andre Z <a.zierfuss....@gmail.com> > > wrote: > > > > > > > Hi, > > > > > > > > I have the following situation. I have set up a http post client > > sending > > > > data to my VM. The VM has a post ressource that passes on the data > to a > > > > kafkaProducer. > > > > > > > > Everything works fine with having the kafkaConsumer inside the VM. > Now > > I > > > > want the cosumer outside and I get a timeout. > > > > > > > > I only changed the IP in the property file to the IP of my VM and I > > > thought > > > > it should work like it does with post. > > > > > > > > > > > > Any thoughts? > > > > > > > > > > > > Thanks, > > > > Andre > > > > > > > > > >
# Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # see kafka.server.KafkaConfig for additional details and defaults ############################# Server Basics ############################# # The id of the broker. This must be set to a unique integer for each broker. brokerid=0 # Hostname the broker will advertise to consumers. If not set, kafka will use the value returned # from InetAddress.getLocalHost(). If there are multiple interfaces getLocalHost # may not be what you want. hostname=192.168.190.195 ############################# Socket Server Settings ############################# # The port the socket server listens on port=9092 # The number of processor threads the socket server uses for receiving and answering requests. # Defaults to the number of cores on the machine num.threads=8 # The send buffer (SO_SNDBUF) used by the socket server socket.send.buffer=1048576 # The receive buffer (SO_RCVBUF) used by the socket server socket.receive.buffer=1048576 # The maximum size of a request that the socket server will accept (protection against OOM) max.socket.request.bytes=104857600 ############################# Log Basics ############################# # The directory under which to store log files log.dir=/tmp/kafka-logs # The number of logical partitions per topic per server. More partitions allow greater parallelism # for consumption, but also mean more files. num.partitions=1 # Overrides for for the default given by num.partitions on a per-topic basis #topic.partition.count.map=topic1:3, topic2:4 ############################# Log Flush Policy ############################# # The following configurations control the flush of data to disk. This is the most # important performance knob in kafka. # There are a few important trade-offs here: # 1. Durability: Unflushed data is at greater risk of loss in the event of a crash. # 2. Latency: Data is not made available to consumers until it is flushed (which adds latency). # 3. Throughput: The flush is generally the most expensive operation. # The settings below allow one to configure the flush policy to flush data after a period of time or # every N messages (or both). This can be done globally and overridden on a per-topic basis. # The number of messages to accept before forcing a flush of data to disk log.flush.interval=10000 # The maximum amount of time a message can sit in a log before we force a flush log.default.flush.interval.ms=1000 # Per-topic overrides for log.default.flush.interval.ms #topic.flush.intervals.ms=topic1:1000, topic2:3000 # The interval (in ms) at which logs are checked to see if they need to be flushed to disk. log.default.flush.scheduler.interval.ms=1000 ############################# Log Retention Policy ############################# # The following configurations control the disposal of log segments. The policy can # be set to delete segments after a period of time, or after a given size has accumulated. # A segment will be deleted whenever *either* of these criteria are met. Deletion always happens # from the end of the log. # The minimum age of a log file to be eligible for deletion log.retention.hours=168 # A size-based retention policy for logs. Segments are pruned from the log as long as the remaining # segments don't drop below log.retention.size. #log.retention.size=1073741824 # The maximum size of a log segment file. When this size is reached a new log segment will be created. log.file.size=536870912 # The interval at which log segments are checked to see if they can be deleted according # to the retention policies log.cleanup.interval.mins=1 ############################# Zookeeper ############################# # Enable connecting to zookeeper enable.zookeeper=true # Zk connection string (see zk docs for details). # This is a comma separated host:port pairs, each corresponding to a zk # server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002". # You can also append an optional chroot string to the urls to specify the # root directory for all kafka znodes. zk.connect=192.168.190.195:2181 # Timeout in ms for connecting to zookeeper zk.connectiontimeout.ms=1000000
