$ cat /etc/krb5.conf
[libdefaults]
udp_preference_limit=1
default_realm = VPC.CLOUDERA.COM
forwardable = true
[realms]
VPC.CLOUDERA.COM = {
@tailrec
def logExceptionChain(e: Throwable): Unit = {
logError("Exception in chain: %s(%s)".format(e.getClass.getName, e.getMessage))
if (e.getCause != null) {
logExceptionChain(e.getCause)
}
}
logExceptionChain(e)
AdminClient
As a general rule, the AdminClient protocol is backward compatible (protocol negotiation happens in the background).
The listed APIs used by Spark are working with metadata API and the latest AdminClient is compatible with it (please see the bullet points for details).
- listTopics:
- describeTopics:
These APIs are working with metadata API, which is an integral part of Kafka almost from the beginning. The functionality has been added in Kafka0.8.1in KAFKA-1227, 17263. Since it exists there were no breaking changes introduced. - listOffsets:
This API is working with metadata API, which is an integral part of Kafka almost from the beginning. The functionality has been added in Kafka0.10.1in KAFKA-4148, 1852 and [1897](https://github.com/apache/kaf
cd "c:\Program Files\Oracle\VirtualBox"
VBoxManage internalcommands createrawvmdk -filename "%USERPROFILE%"\.VirtualBox\usb1.vmdk -rawdisk \\.\PhysicalDrive1
- CDP Private Cloud Base 7.1.5
- Cloudera Runtime Update 7.2.3.0
KafkaConsumer
- assign, subscribe, subscribePattern:
- On topic resourse describe operation
- seek, seekToBeginning, seekToEnd
- On topic resourse describe operation
- poll
- On group resourse read operation
- On topic resourse read operation
- assignment: None
- pause: None
Kafka auto topic creation is an interesting and somewhat really dangerous feature. I would like to write down my findings related this area.
Broker and Consumer side KIP
Producer side KIP
AdminClient side: Not supported in 2.6
The feature is simple when a Producer or Consumer has an assignment with a broker and detects that a topic is deleted
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Format: | |
| appattempt_{clusterTimestamp}_{appId}_{attemptId} | |
| e.g.: appattempt_1410901177871_0001_01. | |
| attemptId starts from 1. |
USERPROFILE=/database/config/db2inst1/sqllib/userprofile
echo "export DB2_KRB5_PRINCIPAL=db2/[email protected]" >> $USERPROFILE
echo "export KRB5_KTNAME=/var/custom/db2.keytab" >> $USERPROFILE
su - db2inst1 -c "db2set DB2ENVLIST=KRB5_KTNAME"