You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Marcus Gründler (JIRA)" <ji...@apache.org> on 2016/04/14 17:44:25 UTC

[jira] [Commented] (KAFKA-3560) Kafka is not working on Solaris

    [ https://issues.apache.org/jira/browse/KAFKA-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241380#comment-15241380 ] 

Marcus Gründler commented on KAFKA-3560:
----------------------------------------

The same is happening when using the multi broker setup as described in the quick start guide.

> Kafka is not working on Solaris
> -------------------------------
>
>                 Key: KAFKA-3560
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3560
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.9.0.0, 0.9.0.1
>         Environment: Solaris 5.10, i386
>            Reporter: Marcus Gründler
>            Priority: Blocker
>         Attachments: controller.log, log-cleaner.log, server.log, state-change.log
>
>
> We are trying to run Kafka 0.9.0.x on Solaris 5.10 but Kafka fails to connect controller to broker at startup. We have no problem running kafka 0.8.2.x on the very same machine. Due to this bug kafka is completely unusable on Solaris.
> We use 1 Broker with the default configuration just as described in the quickstart guide.
> The problem can easily be reproduced by the following steps:
> 1. Download kafka_2.11-0.9.0.1.tgz and unpack.
> 2. Start zookeeper: 
> {noformat}
> bin/zookeeper-server-start.sh config/zookeeper.properties
> {noformat}
> 3. Start kafka: 
> {noformat}
> bin/kafka-server-start.sh config/server.properties
> {noformat}
> 4. Wait 30 seconds
> 5. See timouts in logs/controller.log
> {noformat}
> [2016-04-14 17:01:42,752] WARN [Controller-0-to-broker-0-send-thread], Controller 0's connection to broker Node(0, srvs010.ac.aixigo.de, 9092) was unsuccessful (kafka.controller.RequestSendThread)
> java.net.SocketTimeoutException: Failed to connect within 30000 ms
>         at kafka.controller.RequestSendThread.brokerReady(ControllerChannelManager.scala:228)
>         at kafka.controller.RequestSendThread.liftedTree1$1(ControllerChannelManager.scala:172)
>         at kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:171)
>         at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:63)
> {noformat}
> We can create topics with:
> {noformat}
> bin/kafka-topics.sh --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic test
> {noformat}
> And we can list topics with:
> {noformat}
> bin/kafka-topics.sh --list --zookeeper localhost:2181
> {noformat}
> But we can *not* write data into the topic:
> {noformat}
> bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
> {noformat}
> Our environment is:
> {noformat}
> > uname -a
> SunOS serverXXX 5.10 Generic_147441-16 i86pc i386 i86pc Solaris
> > java -version
> java version "1.8.0_45"
> Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
> {noformat}
> Filesystems we tested are
> * Local file system UFS
> * Network filesystem NFS
> I will provide log files in a minute.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)