Skip to content

Bad cluster configs shouldn't brick the cluster screen #19

Description

@THEjoezack

Sample of a bad config that takes down the cluster page indefinitely:

group.id=grafka
bootstrap.servers=localhost:1234

schema.registry.url=http://localhost:8081

key.serializer=org.apache.kafka.common.serialization.StringSerializer
value.serializer=io.confluent.kafka.serializers.KafkaAvroSerializer

key.deserializer=org.apache.kafka.common.serialization.StringDeserializer
value.deserializer=io.confluent.kafka.serializers.KafkaAvroDeserializer

avro.specific.reader=true

Activity

  1. THEjoezack commented on Nov 18, 2019

    @THEjoezack
    ContributorAuthor

    Maybe it should validate the settings before saving? (In addition to not breaking everything)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions