...
| Code Block |
|---|
|
{
"apiKey": 63,
"type": "request",
"listeners": ["controller"],
"name": "BrokerHeartbeatRequest",
"validVersions": "0-1",
"flexibleVersions": "10+",
"fields": [
...
{ "name": "CordonedLogDirs", "type": "[]uuid", "versions": "1+", "taggedVersions": "2+",
"tag": "1", "about": "Log directories that are cordoned." }
]
} |
...
| Code Block |
|---|
|
{
"apiKey": 35,
"type": "response",
"name": "DescribeLogDirsResponse",
// Starting in version 1, on quota violation, brokers send out responses before throttling.
"validVersions": "0-5",
// Version 2 is the first flexible version.
// Version 3 adds the top-level ErrorCode field
// Version 4 adds the TotalBytes and UsableBytes fields
// Version 5 adds the IsCordoned fields
"flexibleVersions": "2+",
"fields": [
...
{ "name": "IsCordoned", "type": "bool", "versions": "5+", "ignorable": true, "default": false,
"about": "True if this log directory is cordoned."
}
]}
]
} |
Admin API
When describing log directories via the Admin.describeLogDirs() method, you get LogDirDescription objects. A new method will be added to LogDirDescription to tell whether a the log directory is cordoned:
| Code Block |
|---|
|
/**
* A description of a log directory on a particular broker.
*/
public class LogDirDescription {
...
/**
* Whether this log directory is cordoned or not.
*/
public boolean isCordoned() {
...
}
} |
The output of the LogDirsCommand tool will also be updated to show if a log directory is cordoned or not.
Compatibility, Deprecation, and Migration Plan
...