Disable shared open source logging in server tier

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
lkevin1210
Participant
Posts: 5
Joined: Thu Dec 13, 2018 6:11 pm

Disable shared open source logging in server tier

Post by lkevin1210 »

I have recently upgraded datastage from 11.3 to 11.5 fixpack 2 service pack 4, we found that 3 shared open source services are included in this version: zookeeper, kafka and solrcloud.

But these 3 services are not needed for my company, starting them will also consume some cpu resources of the service tier, so we simply turned off the 3 services.

Now the problem comes, the websphere log SystemOut.log & SystemErr.log keep showing error/warning regarding to the 3 services every second and the log file rotation is rapidly filled up.

SystemErr.log

Code: Select all

[2/25/19 17:04:27:442 HKT] 000000db SystemErr     R org.I0Itec.zkclient.exception.ZkTimeoutException: Unable to connect to zookeeper server within timeout: 5000
[2/25/19 17:04:27:442 HKT] 000000db SystemErr     R     at org.I0Itec.zkclient.ZkClient.connect(ZkClient.java:1232)
[2/25/19 17:04:27:443 HKT] 000000db SystemErr     R     at org.I0Itec.zkclient.ZkClient.<init>(ZkClient.java:156)
[2/25/19 17:04:27:443 HKT] 000000db SystemErr     R     at org.I0Itec.zkclient.ZkClient.<init>(ZkClient.java:130)
[2/25/19 17:04:27:443 HKT] 000000db SystemErr     R     at org.I0Itec.zkclient.ZkClient.<init>(ZkClient.java:97)
[2/25/19 17:04:27:443 HKT] 000000db SystemErr     R     at com.ibm.iis.odf.core.messaging.kafka.KafkaMonitor.getZkClient(KafkaMonitor.java:123)
[2/25/19 17:04:27:443 HKT] 000000db SystemErr     R     at com.ibm.iis.odf.core.messaging.kafka.KafkaMonitor.getKafkaBrokers(KafkaMonitor.java:151)
[2/25/19 17:04:27:443 HKT] 000000db SystemErr     R     at com.ibm.iis.odf.core.messaging.kafka.KafkaMonitor.getBrokers(KafkaMonitor.java:218)
[2/25/19 17:04:27:443 HKT] 000000db SystemErr     R     at com.ibm.iis.odf.core.messaging.kafka.KafkaQueueManager.getBootstrapServers(KafkaQueueManager.java:109)
[2/25/19 17:04:27:443 HKT] 000000db SystemErr     R     at com.ibm.iis.odf.core.messaging.kafka.KafkaQueueManager.getConsumerConfigProperties(KafkaQueueManager.java:103

SystemOut.log

Code: Select all

[2/25/19 17:15:03:165 HKT] 00000275 SystemOut     O 05:15:03,165 [container-kafka-consumer-1] ERROR org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer  - Container exception
org.apache.kafka.common.protocol.types.SchemaException: Error reading field 'coordinator': Error reading field 'host': Error reading string of length 25455, only 21 bytes available
        at org.apache.kafka.common.protocol.types.Schema.read(Schema.java:73)
        at org.apache.kafka.clients.NetworkClient.parseResponse(NetworkClient.java:380)
        at org.apache.kafka.clients.NetworkClient.handleCompletedReceives(NetworkClient.java:449)
        at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:269)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.clientPoll(ConsumerNetworkClient.java:360)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:224)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:192)
        at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:163)
        at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureCoordinatorReady(AbstractCoordinator.java:179)
        at org.apache.kafka.clients.consumer.KafkaConsumer.pollOnce(KafkaConsumer.java:974)
        at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:938)
        at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.run(KafkaMessageListenerContainer.java:531)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522)
        at java.util.concurrent.FutureTask.run(FutureTask.java:277)
        at java.lang.Thread.run(Thread.java:811)

I believe that it is because websphere found the 3 services are not started so there is error/warnings come out.

My question is can we disable websphere from checking the status of zookeeper, kafka and solrcloud, so we can avoid the error/warnings keep showing in SystemOut.log and SystemErr.log?.

Thanks in advance (and sorry for my little knowledge of the 3 services, I am not so sure if it is possible to disable checking them in websphere log). :oops:
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Information Server DOES need them. As versions progress into the future, you will find that more and more pieces of IIS are deployed as Docker containers, managed by Kubernetes kubectl and other commands. Some of the services are deployed as Zookeeper services. Turn them back on, or IIS will not work.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply