1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Phoebus AlarmClientModel console messages |
From: | John Dobbins via Tech-talk <tech-talk at aps.anl.gov> |
To: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Thu, 11 Jun 2020 23:05:05 +0000 |
All,
We are running the Phoebus Kafka based alarm handler. When we run an alarm client, which works, we see in the console a steady stream of messages along the lines shown below. Are these normal messages? Is there a way to adjust the console logging level when
launching Phoebus?
Regards,
John Dobbins
Research Support Specialist
Cornell High Energy Synchrotron Source
Cornell University
www.chess.cornell.edu
18:57:46.292 [AlarmClientModel CHESS] DEBUG org.apache.kafka.clients.consumer.internals.ConsumerCoordinator - [Consumer clientId=consumer-2, groupId=Alarm-071c7feb-e977-4215-b0bf-fc7a7c9adec8] Completed asynchronous auto-commit of offsets {CHESS-0=OffsetAndMetadata{offset=69952,
metadata=''}}
18:57:46.297 [AlarmClientModel CHESS] DEBUG org.apache.kafka.clients.consumer.internals.ConsumerCoordinator - [Consumer clientId=consumer-3, groupId=Alarm-dbc66a46-5e59-4928-b74b-7aca05ca4e94] Committed offset 69952 for partition CHESS-0
18:57:46.308 [AlarmClientModel CHESS] DEBUG org.apache.kafka.clients.consumer.internals.ConsumerCoordinator - [Consumer clientId=consumer-3, groupId=Alarm-dbc66a46-5e59-4928-b74b-7aca05ca4e94] Completed asynchronous auto-commit of offsets {CHESS-0=OffsetAndMetadata{offset=69952,
metadata=''}}
18:57:46.362 [AlarmClientModel CHESS] DEBUG org.apache.kafka.clients.FetchSessionHandler - [Consumer clientId=consumer-2, groupId=Alarm-071c7feb-e977-4215-b0bf-fc7a7c9adec8] Node 1 sent an incremental fetch response for session 94643207 with 0 response
partition(s), 1 implied partition(s)
18:57:46.374 [AlarmClientModel CHESS] DEBUG org.apache.kafka.clients.consumer.internals.Fetcher - [Consumer clientId=consumer-2, groupId=Alarm-071c7feb-e977-4215-b0bf-fc7a7c9adec8] Added READ_UNCOMMITTED fetch request for partition CHESS-0 at offset 69952
to node chess-kafka1:9092 (id: 1 rack: null)
18:57:46.392 [AlarmClientModel CHESS] DEBUG org.apache.kafka.clients.FetchSessionHandler - [Consumer clientId=consumer-2, groupId=Alarm-071c7feb-e977-4215-b0bf-fc7a7c9adec8] Built incremental fetch (sessionId=94643207, epoch=36) for node 1. Added 0 partition(s),
altered 0 partition(s), removed 0 partition(s) out of 1 partition(s)
18:57:46.401 [AlarmClientModel CHESS] DEBUG org.apache.kafka.clients.consumer.internals.Fetcher - [Consumer clientId=consumer-2, groupId=Alarm-071c7feb-e977-4215-b0bf-fc7a7c9adec8] Sending READ_UNCOMMITTED IncrementalFetchRequest(toSend=(), toForget=(),
implied=(CHESS-0)) to broker chess-kafka1:9092 (id: 1 rack: null)
|