hi @araujo    the userPrincipalName of user livy is:   livy/hostname_livy_server@DOMAIN.LOCAL     the userPrincipalName of the livy-http user is:   livy-http@DOMAIN.LOCAL     running the command "kinit livy":     running the command "kinit livy-http":     running the "kinit" command with the keytab created for user livy:     running the command "kinit" with the keytab created for the user livy-http:     we've been facing this problem for months, we haven't found the solution yet. ... View more

hi @Scharan    the same goes for sentry? ... View more

hi @Asfahan    checking the file with the same name as tablet_id in the "consensus-meta" directory, it shows that the file is 11K in all TS   as you can see in the screenshot below, the tablet_id has different sizes between the 3 TS   ... View more

hi @Deepan_N    by running the command below directly in python3:   r0.headers["www-authenticate"]   returns the following error:   Python 3.6.8 (default, Nov 16 2020, 16:55:22) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> r0.headers["www-authenticate"] Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'r0' is not defined >>> below is the screenshot of the commands executed in bash:   ... View more

@yagoaparecidoti    A] Generally /config/topics/ will store all topic level configuration if you have set any.   For example: If you have set any topic level setting then it will be stored there:   [zk: node1.zookeeper-hostname.com:2181(CONNECTED) 6] get /kafka/config/topics/ATLAS_HOOK {"version":1,"config":{"retention.ms":"2678400000","cleanup.policy":"compact"}} [zk:node1.zookeeper-hostname.com:2181(CONNECTED) 7]   Here topic level settings are retention.ms and cleanup.policy=compact   As it has only topic-level configuration details it will not affect the Kafka cluster or applications if applications are not dependent on any topic-level settings.    B] There is no standard Kafka tool which you can use to restore /config/topics but you can easily alter/set topic level settings using the Kafka command below as per your retirement if any.    kafka-configs --zookeeper <ZK_host>:2181/kafka --entity-type topics --entity-name <topic_name> --alter --add-config <configname & value>   Note: Replace all required settings and /kafka (/kafka can be checked from CM >> Kafka >> Conf >> zookeeper.chroot) in the above command   If you found this response assisted with your query, please take a moment to log in and click on  KUDOS 🙂 & ”Accept as Solution" below this post. ... View more