2017-04-06 44 views
0

我試圖根據在http://cloud.spring.io/spring-cloud-dataflow/中解釋的非常簡單的示例運行「Hello,world」Spring雲數據流。我能夠創建一個簡單的源代碼和接收器,並使用Kafka在我的本地SCDF服務器上運行它,所以在此之前一切都是正確的。Spring雲數據流> Stream> Source在K8s中部署但在本地部署中工作時拋出UNKNOWN_TOPIC_OR_PARTITION

現在,我試圖根據http://docs.spring.io/spring-cloud-dataflow-server-kubernetes/docs/current-SNAPSHOT/reference/htmlsingle/#_getting_started中列出的說明將其部署到我的私有云中。使用此部署,我可以部署一個簡單的「time | log」開箱即用的流,但沒有問題,但我的示例失敗。

特定版本:

  • 泊塢版本1.13.1,構建092cba3
  • Hyperkube 1.5.5
  • 新加坡民防部隊1.2.0.M2
  • 飼養員3.4.9-1757313,建2016年8月23日06:50 GMT
  • 卡夫卡0.10.1.1

源項目日誌有:

2017-04-06T11:05:07.429204866Z 2017年4月6日11:05:07428 INFO主SendThread(10.0.0.181:2181)oazClientCnxn:876 - 插座連接建立至10.0。 0.181/10.0.0.181:2181,啓動會話 2017-04-06T11:05:07.440381666Z 2017-04-06 11:05:07,439信息main-SendThread(10.0.0.181:2181)oazClientCnxn:1299 - 會話建立完成on server 10.0.0.181/10.0.0.181:2181,sessionid = 0x15b155ef61e014a,negotiated timeout = 10000 2017-04-06T11:05:07.740130495Z 2017-04-06 11:05:07,737信息main oakcpProducerConfig:180 - ProducerConfig values : 2017-04-06T11:05:07.740160464Z acks = 1 2017-04-06T11:05:07.740163408Z batch.size = 16384 2017-04-06T11:05:07.740165226Z block.on.buffer.full = false 2017-04-06T11:05:07.740166942Z bootstrap.servers = [10.0.0.213:9092] 2017-04-06T11:05: 07.740168741Z buffer.memory = 33554432 2017-04-06T11:05:07.740170545Z client.id = 2017-04-06T11:05:07.740172245Z compression.type =無 2017-04-06T11:05:07.740173971Z連接.max.idle.ms = 540000 2017-04-06T11:05:07.740175706Z interceptor.classes = null 2017-04-06T11:05:07.744179899Z reconnect.backoff.ms = 50 2017-04-06T11:05 :07.744181600Z request.timeout.ms = 30000 2017-04-06T11:05:07.744183356Z retries = 0 2017-04-06T11:05:07.744185083Z retry.backoff.ms = 100 2017-04-0 6T11:05:07.744186754Z sasl.kerberos.kinit.cmd =/usr/bin/kinit 2017-04-06T11:05:07.744188494Z sasl.kerberos.min.time.before.relogin = 60000 2017-04-06T11 :05:07.744190205Z sasl.kerberos.service.name = NULL 2017-04-06T11:05:07.744191916Z sasl.kerberos.ticket.renew.jitter = 0.05 2017-04-06T11:05:07.744193763Z sasl.kerberos .ticket.renew.window.factor = 0.8 2017-04-06T11:05:07.744195432Z sasl.mechanism = GSSAPI 2017-04-06T11:05:07.744197163Z security.protocol = PLAINTEXT 2017-04-06T11:05 :07.744198789Z send.buffer.bytes = 131072 2017-04-06T11:05:07.744200522Z ssl.cipher.suites = null 2017-04-06T11:05:07.744202328Z ssl.enabled.protocols = [TLSv1.2, TLSv1.1,TLSv1] 2017-04-06T11:05:07.744204161Z ssl.endpoint.identification.algorithm = null 2017-04-06T11:05:07.744205837Z ssl.key。密碼= null 2017-04-06T11:05:07.744207544Z ssl.keymanager.algorithm = SunX509 2017-04-06T11:05:07.744212464Z ssl.keystore.location = null 2017-04-06T11:05:07.744214272Z ssl.keystore.password = NULL 2017-04-06T11:05:07.744216025Z ssl.keystore.type = JKS 2017-04-06T11:05:07.744217647Z ssl.protocol = TLS 2017-04-06T11:05: 07.744219234Z ssl.provider = null 2017-04-06T11:05:07.744220987Z ssl.secure.random.implementation = null 2017-04-06T11:05:07.744222666Z ssl.trustmanager.algorithm = PKIX 2017-04- 06T11:05:07.744224359Z ssl.truststore.location = null 2017-04-06T11:05:07.744226022Z ssl.truststore.password = null 2017-04-0 6T11:05:07.744228171Z ssl.truststore.type = JKS 2017-04-06T11:05:07.744230006Z timeout.ms = 30000 2017-04-06T11:05:07.744231705Z value.serializer = class org.apache.kafka .common.serialization.ByteArraySerializer 2017-04-06T11:05:07.744233544Z 2017-04-06T11:05:07.837193978Z 2017年4月6日11:05:07834 WARN主oakcpProducerConfig:188 - 配置「鍵。反序列化器「被提供,但不是已知的配置。 2017-04-06T11:05:07.837221870Z 2017-04-06 11:05:07,835 WARN main o.a.k.c.p.ProducerConfig:188 - 配置'value.deserializer'被提供,但不是已知的配置。 2017-04-06T11:05:07.929207703Z 2017年4月6日11:05:07926信息主要oakcuAppInfoParser:83 - 卡夫卡版本:0.10.1.1 2017-04-06T11:05:07.929239636Z 2017年4月6日11:05:07,927信息main oakcuAppInfoParser:84 - Kafka commitId:f10ef2720b03b247 2017-04-06T11:05:08.228817026Z 2017-04-06 11:05:08,228 WARN kafka-producer-network-thread | producer-1 oakcNetworkClient:600 - 使用相關標識獲取元數據時出錯0:{output = UNKNOWN_TOPIC_OR_PARTITION} 2017-04-06T11:05:08.436574800Z 2017-04-06 11:05:08,435 WARN kafka-producer-network-線程|生產者 - 1 oakcNetworkClient:600 - 錯誤擷取與元數據相關性id 1:{輸出= UNKNOWN_TOPIC_OR_PARTITION}

而且Zookepeer日誌:

2017-04-06T11:04:38.000953447Z 2017 -04-06 11:04:38000 [本身份識別碼:] - INFO [ProcessThread(SID:0 CPORT:2181):: PrepRequestProcessor @ 487] - 爲的sessionid耗時會話終止:0x15b155ef61e0148 2017-04-06T11:05:04.939356606Z 2017-04-06 11:05:04,938 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory @ 192] - 從/10.1.98.5:48180接受套接字連接 2017-04 -06T11:05:04.940666418Z 2017 -04-06 11:05:04,939 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer @ 928] - 客戶端嘗試建立新會話/10.1.98.5:48180 2017 -04-06T11:05:04.943859474Z 2017-04-06 11:05:04,943 [myid:] - INFO [SyncThread:0:ZooKeeperServer @ 673] - 建立會話0x15b155ef61e0149,協商超時10000 for client /10.1.98.5:48180 2017-04-06 11:05:07,325 [myid:] - INFO [ProcessThread(sid:0 cport:2181):: PrepRequestProcessor @ 487] - 爲sessionid處理的會話終止: 0x15b155ef61e0149 2017-04-06T11:05:07.342876962Z 2017年4月6日11:05:07341 [本身份識別碼:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn @ 1008] - 閉插座連接客戶端/10.1.98.5:48180其中sessionid 0x15b155ef61e0149 2017-04-06T11:05:07.429909440Z 2017-04-06 11:05:07,429 [myid:] - INFO [NIOServer Cxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory @ 192] - 從/10.1.98.5:48182接受套接字連接 2017-04-06T11:05:07.429933377Z 2017-04-06 11:05:07,429 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer @ 928] - 客戶端嘗試建立新會話/10.1.98.5:48182 2017-04-06T11:05:07。441158222Z 2017-04-06 11:05:07,439 [myid:] - INFO [SyncThread:0:ZooKeeperServer @ 673] - 建立會話0x15b155ef61e014a,協商超時10000 for client /10.1.98.5:48182 2017-04-06T11:05 :29.695276997Z 2017-04-06 11:05:29,694 [myid:] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn @ 357] - 捕捉異常結束 2017-04-06T11 :05:29.695325790Z EndOfStreamException:無法從客戶端sessionid 0x15b155ef61e014a讀取其他數據,可能客戶端已關閉套接字 2017-04-06T11:05:29.695328912Z at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java: 228) 2017-04-06T11:05:29.695331119Z at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203) 2017-04-06T11:05:29.695333009Z at java.lang.Thread。運行(Thread.java:745) 2017-04-06T11:05:29.696333706Z 2017-04-06 11:05:29,696 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn @ 1008] - 封閉的套接字連接客戶端

我沒有發現任何登錄卡夫卡在異常的時刻。

用於源類代碼段是

package xxxx; 

import java.text.SimpleDateFormat; 
import java.util.Date; 

import org.springframework.boot.SpringApplication; 
import org.springframework.boot.autoconfigure.SpringBootApplication; 
import org.springframework.cloud.stream.annotation.EnableBinding; 
import org.springframework.cloud.stream.messaging.Source; 
import org.springframework.context.annotation.Bean; 
import org.springframework.integration.annotation.InboundChannelAdapter; 
import org.springframework.integration.core.MessageSource; 
import org.springframework.messaging.support.GenericMessage; 

@SpringBootApplication 
@EnableBinding(Source.class) 
public class HelloNitesApplication 
{ 
    public static void main(String[] args) 
    { 
     SpringApplication.run(HelloNitesApplication.class, args); 
    } 

    @Bean 
    @InboundChannelAdapter(value = Source.OUTPUT) 
    public MessageSource<String> timerMessageSource() 
    { 
     return() -> new GenericMessage<>("Hello " + new SimpleDateFormat().format(new Date())); 
    } 

所以,包含流源吊艙保持在一個循環崩潰。

回答

0

這個問題似乎是由於我的實現忽略了屬性「spring.cloud.stream.bindings.output.destination = XXX」,我在執行前刪除了主題「output」,因爲我期望它寫入屬性指定的主題。

在我重新部署所有源代碼之後,當主題被正確創建時,雖然在「output」主題中插入消息,而不是由我定義的屬性指定的消息。

相關問題