# US 2012/0084753 A1 · Debugger launch and attach on compute clusters

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0084753 A1
- Document ID: US20120084753A1
- Status: Published application
- Kind: A1
- Application number: 12/894,590
- Filed: 2010-09-30
- Published: 2012-04-05
- Earliest claimed: 2010-09-30
- Assignees: Microsoft Corporation
- Inventors: Paul E. Maybee; Daniel Moth; Gregg Bernard Miskelly
- Web page: https://patentgrep.com/patent/US20120084753A1

## CPC

- G06F 11/362: Debugging of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Launching a debugging process. A method includes at a compute node on a cluster private network, receiving a debug job via a scheduler of a head node from a client on a public network. The head node is connected to both the cluster private network and the public network. The public network is external to the cluster private network. The method further includes beginning processing the debug job, and as a result initiating debugging by starting one or more debugger remote agents at the compute node. The method further includes beginning processing a user job in the presence of the started debugger remote agents at the compute node. The client is informed that the one or more debugger remote agents are ready to debug the user job. A debugger client at the client is connected to the one or more debugger remote agents.

## Claims

### Claim 1

In a computing environment comprising a cluster computing system, a method of launching a debugging process, the method comprising:
at a compute node on a cluster private network, receiving a debug job via a scheduler of a head node from a client on a public network, wherein the head node is connected to both the cluster private network and the public network, and wherein the public network is external to the cluster private network;
beginning processing the debug job, and as a result initiating debugging by starting one or more debugger remote agents at the compute node;
beginning processing a user job in the presence of the started debugger remote agents at the compute node;
informing the client that the one or more debugger remote agents are ready to debug the user job; and
as a result connecting a debugger client at the client to the one or more debugger remote agents.

### Claim 2 (depends on 1)

The method of claim 1 wherein the client comprises a listener and wherein communication from the client to the compute node via one or more intermediaries is from the listener.

### Claim 3 (depends on 2)

The method of claim 2, wherein communications are pulled from the client.

### Claim 4 (depends on 2)

The method of claim 2, wherein communications are pushed from the client.

### Claim 5 (depends on 1)

The method of claim 1, wherein communications between the client and the compute node are through a proxy on a system coupled to both the public network and the cluster private network.

### Claim 6 (depends on 1)

The method of claim 1, wherein communications between the client and the compute node are through a NAT service on a system coupled to both the public network and the cluster private network.

### Claim 7 (depends on 1)

The method of claim 1 further comprising receiving the user job via the scheduler of the head node from the client on the public network.

### Claim 8 (depends on 1)

The method of claim 1 further comprising opening one or more proxy ports to facilitate communications between the client and the compute node, and wherein the one or more proxy ports are selected from the range of 13225 to 13719.

### Claim 9 (depends on 1)

The method of claim 1, wherein the client comprises a developer application used by a developer to develop application for cluster computing, and wherein messages from the client are received from the developer application.

### Claim 10

In a computing environment comprising a cluster computing system, a method of attaching a debugging process, the method comprising:
at a compute node on a cluster private network that is executing a user job, receiving a message to start a debug job from a client on a public network, via a system that is connected to both the cluster private network and the public network, and wherein the public network is external to the cluster private network
beginning processing the debug job, and as a result initiating debugging of the user job, by starting one or more debugger remote agents at the compute node;
informing the client that the one or more debugger remote agents are ready to debug the user job; and
as a result connecting a debugger client at the client to the one or more debugger remote agents.

### Claim 11 (depends on 10)

The method of claim 10 wherein the client comprises a listener and wherein communication from the client to the compute node via one or more intermediaries is from the listener.

### Claim 12 (depends on 11)

The method of claim 11, wherein communications are pulled from the client.

### Claim 13 (depends on 11)

The method of claim 11, wherein communications are pushed from the client.

### Claim 14 (depends on 10)

The method of claim 10, wherein communications between the client and the compute node are through a proxy on a system coupled to both the public network and the cluster private network.

### Claim 15 (depends on 10)

The method of claim 10, wherein communications between the client and the compute node are through a NAT service on a system coupled to both the public network and the cluster private network.

### Claim 16 (depends on 10)

The method of claim 10 further comprising receiving the user job via a scheduler of the head node from the client on the public network.

### Claim 17 (depends on 10)

The method of claim 10 further comprising opening one or more proxy ports to facilitate communications between the client and the compute node, and wherein the one or more proxy ports are selected from the range of 13225 to 13719.

### Claim 18 (depends on 10)

The method of claim 10, wherein the client comprises a developer application used by a developer to develop application for cluster computing, and wherein messages from the client are received from the developer application.

### Claim 19

In a computing environment comprising a cluster computing system, a method of launching a debugging process using NAT forwarding, the method comprising:
at a developer application, receiving user input requesting that a job be scheduled for execution on a cluster;
at the developer application, sending the job to a scheduler;
at the scheduler, queuing the job for execution on the cluster;
at the scheduler, assigning a set of compute nodes to the job causing the job to start running on each compute node;
wherein a first task in the job is a debug start task, executing the debug start task causing a remote agent process to be created at each compute node in the set of compute nodes;
each remote agent opening a first port and listening on the first port for debugger connections from a debugger at the developer application;
registering the first port on each compute agent with a directory service;
at the developer application polling the directory service for all the ports registered for the job until the developer application receives one mapped port for each remote agent, wherein the directory service creates port mappings via NAT as needed to fulfill poll requests;
the directory service periodically polling the scheduler to verify that the job has not terminated;
for each registered port registered at the directory service, the developer application connecting to the remote agent on a corresponding compute node and creating and debugging a user process with messages continuing back and forth between the developer application and the remote agent until the debugging session is complete; and
the directory service discovering that the debugging session is complete and deleting all forwarding ports.

### Claim 20 (depends on 19)

The method of claim 19, wherein the developer application is implemented on a client connected on public network, the directory service and scheduler are implemented on a head node on both a cluster private network and the public network, and wherein the public network is external to the cluster private network, and the remote agent is implemented on the cluster private network.
