Post to Monasca Log API can exceed Kafka max size
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Incomplete
|
Low
|
Doug Szumski |
Bug Description
We have 10MB limit on the Monasca API, to accept the maximum Fluentd chunks of 8MB. When we make a post larger than 1MB, we see:
Error{code=
2020-07-24 14:12:56.649 26 ERROR monasca_
68bd3f4b4389e07abb - default default] ('Service unavailable', 'KafkaError{
oo large"}', 60): falcon.
er: Message size too large"}', 60)
2020-07-24 14:12:56.649 26 ERROR monasca_
2020-07-24 14:12:56.649 26 ERROR monasca_
isher.py", line 181, in _publish
2020-07-24 14:12:56.649 26 ERROR monasca_
2020-07-24 14:12:56.649 26 ERROR monasca_
oducer.py", line 77, in publish
2020-07-24 14:12:56.649 26 ERROR monasca_
2020-07-24 14:12:56.649 26 ERROR monasca_
ssage: Broker: Message size too large"}
2020-07-24 14:12:56.649 26 ERROR monasca_
2020-07-24 14:12:56.649 26 ERROR monasca_
2020-07-24 14:12:56.649 26 ERROR monasca_
2020-07-24 14:12:56.649 26 ERROR monasca_
2020-07-24 14:12:56.649 26 ERROR monasca_
sor.py", line 66, in send_message
2020-07-24 14:12:56.649 26 ERROR monasca_
2020-07-24 14:12:56.649 26 ERROR monasca_
isher.py", line 186, in _publish
2020-07-24 14:12:56.649 26 ERROR monasca_
2020-07-24 14:12:56.649 26 ERROR monasca_
OO_LARGE,
2020-07-24 14:12:56.649 26 ERROR monasca_
This is with the Confluent Kafka client and the unified Monasca API. Possibly something has changed.
Can resolve with the following Kafka config in Kafka server.properties (on the large side):
message.max.bytes = 104857600
replica.
Tempest Log API tests assumes anything >1MB is too big and are not configurable.
Changed in kolla-ansible: | |
assignee: | nobody → Doug Szumski (dszumski) |
Changed in kolla-ansible: | |
importance: | Undecided → Medium |
Is that still something you'd like to pursue Doug? Putting the ticket in Incomplete status, will get expired in 60 days if no updates are written here.