[ 
https://issues.apache.org/jira/browse/KUDU-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18146885#comment-18146885
 ] 

ASF subversion and git services commented on KUDU-3806:
-------------------------------------------------------

Commit a786e784452aff5339cfb7c8e1343a261d1f6aff in kudu's branch 
refs/heads/master from Ashwani Raina
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=a786e7844 ]

[tools] classify per-location quiesce/state actions for MCP

Commit 4233503cb (KUDU-3811) added the 'kudu cluster location quiesce'
and 'kudu cluster location state' modes, but it landed after commit
cc0533d6a (KUDU-3806), which requires every CLI action to set an MCP
disposition. The new actions didn't set one. As a result,
McpDispositionTest.ValidateCoveragePassesAgainstCurrentTree failed with:

  Not found: CLI action is not classified for the MCP server (missing
  ActionBuilder::McpDisposition): 'cluster location quiesce status'

and 'kudu mcp serve' would crash at startup in
ValidateDispositionCoverageOrDie().

This patch classifies the five per-location actions the same way as
their per-tablet-server counterparts under 'kudu tserver':
  cluster location quiesce status            SURFACE
  cluster location quiesce start             GATED
  cluster location quiesce stop              GATED
  cluster location state enter_maintenance   GATED
  cluster location state exit_maintenance    GATED

Change-Id: I4009906169bf0f8fa989d4cf1d304d0f90d9ef1e
Co-authored-by: Cursor <[email protected]>
Reviewed-on: https://gerrit.cloudera.org/25470
Reviewed-by: Gabriella Lotz <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
Tested-by: Alexey Serbin <[email protected]>


> Kudu MCP
> --------
>
>                 Key: KUDU-3806
>                 URL: https://issues.apache.org/jira/browse/KUDU-3806
>             Project: Kudu
>          Issue Type: New Feature
>            Reporter: Marton Greber
>            Assignee: Marton Greber
>            Priority: Major
>
>  Introduce kudu mcp serve, an MCP server that exposes existing kudu CLI 
> actions as MCP tools so operators can drive cluster diagnostics and 
> administration from an MCP-capable client (e.g. an LLM agent) without 
> hand-crafting command lines.
> Design highlights:
>  - Safety classification. Every action in the CLI action tree resolves to 
> exactly one Disposition:
>  -- SURFACE — read-only, always exposed (node-local reads are surfaced but 
> tagged as only meaningful on that node);
>  -- GATED — cluster-mutating, hidden unless --allow-writes is set;
>  -- REJECT — long-running/never-promptly-returning ops that would wedge the 
> single-threaded serve loop;
>  -- EXCLUDE — interactive or node-local mutating actions, never surfaced.
>  - Read-only by default. Mutating tools are only advertised with 
> --allow-writes.
>  - Process isolation. Each tools/call runs its action in a fresh child kudu 
> process bounded by --mcp_tool_timeout_sec (default 60s), so a hung action 
> cannot freeze the server.
>  - Credential hygiene. --master_addresses is registered once at serve time 
> and injected into each call, so it never has to appear in the conversation.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to