我正在使用Apache Storm 1.1.2,Apache Kafka 0.10,Zookeeper和Docker Compose编写一个dockerized Java 9 Spring应用程序。
我的拓扑结构完全在我的dockerized服务中的本地集群上工作,但现在我将它移动到生产集群有一个问题。
我为Storm集群创建提交拓扑的服务似乎工作正常,代码在PostConstruct中看起来很像这样
KafkaSpoutConfig<String,String> spoutConf =
KafkaSpoutConfig.builder("kafka:9092", "topic")
.setProp(ConsumerConfig.GROUP_ID_CONFIG, "my-group-id")
.setProp(ConsumerConfig.VALUE_DESERIALIZER_CLASS_CONFIG, MyDeserializer.class)
.build();
TopologyBuilder builder = new TopologyBuilder();
builder.setSpout("kafkaSpoutId", new KafkaSpout<String,String>(spoutConf));
builder.setBolt("boltId", new MyBolt()).shuffleGrouping("kafkaSpoutId");
Config conf = new Config();
conf.setNumWorkers(2);
conf.put(Config.STORM_ZOOKEEPER_SERVERS, List.of("zookeeper"));
conf.put(Config.STORM_ZOOKEEPER_PORT, 2181);
conf.put(Config.NIMBUS_SEEDS, List.of("nimbus"));
conf.put(Config.NIMBUS_THRIFT_PORT, 6627);
System.setProperty("storm.jar","/opt/app.jar");
StormSubmitter.submitTopology("topology-id", conf, builder.createTopology());
我的docker撰写文件看起来像这样。
version: "2.1"
services:
my-service:
image: my-service
mem_limit: 4G
memswap_limit: 4G
networks:
- default
environment:
- SPRING_PROFILES_ACTIVE=local
nimbus:
image: storm:1.1.2
container_name: nimbus
command: >
storm nimbus
-c storm.zookeeper.servers="[\"zookeeper\"]"
-c nimbus.seeds="[\"nimbus\"]"
networks:
- default
ports:
- 6627:6627
supervisor:
image: storm:1.1.2
container_name: supervisor
command: >
storm supervisor
-c storm.zookeeper.servers="[\"zookeeper\"]"
-c nimbus.seeds="[\"nimbus\"]"
networks:
- default
depends_on:
- nimbus
links:
- nimbus
restart: always
ports:
- 6700
- 6701
- 6702
- 6703
ui:
image: storm:1.1.2
command: storm ui -c nimbus.seeds="[\"nimbus\"]"
networks:
- default
ports:
- 8081:8080
networks:
default:
external:
name: myNetwork
所有的容器都装满了。在UI中,我可以看到在post构造中创建的拓扑但是没有正在处理Kafka消息,并且应该使用本地Kafka生成器生成聚合的bolt不会发布。
在/logs/worker-artifact/topology-id****/6700/worker.log
的主管容器中,我可以看到重复的两个例外。
第一个(我认为更重要的)是ClassNotFoundException: org.apache.storm.kafka.spout.KafkaSpout
第二个例外是org.apache.storm.shade.org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6700
UPDATE
不幸的是,我无法发布我的整个pom,但这里是我的Storm依赖项
<dependency>
<groupId>org.apache.storm</groupId>
<artifactId>storm-core</artifactId>
<version>${storm.version}</version>
</dependency>
<dependency>
<groupId>org.apache.storm</groupId>
<artifactId>storm-kafka-client</artifactId>
<version>${storm.version}</version>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
</dependency>
这是我的spring-boot-maven-plugin。我虽然添加了配置来使复制到我的容器不可执行的jar可以解决问题。当我检查容器中的jar时,它看起来依赖的行包括jar但是还有大量的乱码字符
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<executable>false</executable>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
</plugin>
</plugins>
</build>
这是我的dockerfile的大部分内容
FROM ${docker.repository}/openjdk:9.0.1
EXPOSE 80 1099
WORKDIR /opt
ENTRYPOINT ["java", \
"-Dinfo.serviceName=${project.artifactId}", \
"-Dinfo.serviceVersion=${project.version}"]
CMD ["-jar", "app.jar"]
LABEL VERSION="${project.version}" DESCRIPTION="${project.description}"
COPY ${project.build.finalName}-exec.jar /opt/app.jar
我想到了。问题是我正在形成一个不可执行的jar但不是一个真正的胖罐。我把以下的下巴加入了我的pom
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
接下来,我将System属性更改为System.setProperty("storm.jar", "/opt/storm.jar");
并将以下行添加到我的Dockerfile中
COPY ${project.build.finalName}-jar-with-dependencies.jar /opt/storm.jar
最后我会首先运行mvn comiple assembly:single
然后从项目目录cp target/project-jar-with-dependencies.jar target/docker-ready/
复制项目jar从目标/到target / docker-ready依赖项目jar,最后运行mvn verify docker:build