Summary

The unassignTasks() GraphQL mutation may be used to unassign node tasks. It returns the set of assigned tasks after the unassign operation has completed.

API Stability Short-Term

Syntax

graphql
unassignTasks(
     nodeID: integer!,
     tasks: [NodeTaskEnum]!
   ): [NodeTaskEnum]!

You'll have to give the number of the node in the cluster. You'll also have to give a list of tasks to unassign.

For the results, you can get a list of tasks left in place. See the Returned Values section.

Example

Raw
graphql
mutation {
  unassignTasks(
    nodeID: 1, 
    tasks: [storage, query]
  )
}
Mac OS or Linux (curl)
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
    -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" \
    -d @- << EOF
{"query" : "mutation {
  unassignTasks(
    nodeID: 1, 
    tasks: [storage, query]
  )
}"
}
EOF
Mac OS or Linux (curl) One-line
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
    -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" \
    -d @- << EOF
{"query" : "mutation {
  unassignTasks(
    nodeID: 1, 
    tasks: [storage, query]
  )
}"
}
EOF
Windows Cmd and curl
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql ^
    -H "Authorization: Bearer $TOKEN" ^
    -H "Content-Type: application/json" ^
    -d @'{"query" : "mutation { ^
  unassignTasks( ^
    nodeID: 1,  ^
    tasks: [storage, query] ^
  ) ^
}" ^
} '
Windows Powershell and curl
powershell
curl.exe -X POST 
    -H "Authorization: Bearer $TOKEN"
    -H "Content-Type: application/json"
    -d '{"query" : "mutation {
  unassignTasks(
    nodeID: 1, 
    tasks: [storage, query]
  )
}"
}'
    "$YOUR_LOGSCALE_URL/graphql"
Perl
perl
#!/usr/bin/perl

use HTTP::Request;
use LWP;

my $TOKEN = "TOKEN";

my $uri = '$YOUR_LOGSCALE_URL/graphql';

my $query = "mutation {
  unassignTasks(
    nodeID: 1, 
    tasks: [storage, query]
  )
}";
$query =~ s/\n/ /g;
my $json = sprintf('{"query" : "%s"}',$query);
my $req = HTTP::Request->new("POST", $uri );

$req->header("Authorization" => "Bearer $TOKEN");
$req->header("Content-Type" => "application/json");

$req->content( $json );

my $lwp = LWP::UserAgent->new;

my $result = $lwp->request( $req );

print $result->{"_content"},"\n";
Python
python
#! /usr/local/bin/python3

import requests

url = '$YOUR_LOGSCALE_URL/graphql'
mydata = r'''{"query" : "mutation {
  unassignTasks(
    nodeID: 1, 
    tasks: [storage, query]
  )
}"
}'''

resp = requests.post(url,
                     data = mydata,
                     headers = {
   "Authorization" : "Bearer $TOKEN",
   "Content-Type" : "application/json"
}
)

print(resp.text)
Node.js
javascript
const https = require('https');

const data = JSON.stringify(
    {"query" : "mutation {
  unassignTasks(
    nodeID: 1, 
    tasks: [storage, query]
  )
}"
}
);


const options = {
  hostname: '$YOUR_LOGSCALE_URL',
  path: 'graphql',
  port: 443,
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Content-Length': data.length,
    Authorization: 'BEARER ' + process.env.TOKEN,
    'User-Agent': 'Node',
  },
};

const req = https.request(options, (res) => {
  let data = '';
  console.log(`statusCode: ${res.statusCode}`);

  res.on('data', (d) => {
    data += d;
  });
  res.on('end', () => {
    console.log(JSON.parse(data).data);
  });
});

req.on('error', (error) => {
  console.error(error);
});

req.write(data);
req.end();
Example Responses
Success (HTTP Response Code 200 OK)
json
{
  "data": {
    "unassignTasks": [
      "digest"
    ]
  }
}

Input Parameters

For the input, you would need to provide the number of the node in the cluster. You'll also have to give a list of tasks to unassign. It uses the same datatype as the returned datatype (see the Returned Values section).

Table: Input Parameters & Datatypes

Parameter Type Required Default Description
This table contains all input parameters for this mutation. Since one of the parameters uses a special datatype, an additional table is included below with its parameters.
nodeID integer yes   The number of the node in the cluster.
tasks [NodeTaskEnum] yes   A comma-separated list of tasks to unassign. See table in Returned Values section.

Returned Values

For the returned values there is an enumerated list with only couple of choices. They're listed and described here:

Table: NodeTaskEnum Enum Datatype

ParameterTypeRequiredDefaultStabilityDescription
Some input parameters may be required, as indicated in the Required column. For return values, this indicates that you are assured a value if the field is requested for the results.
Table last updated: Jun 23, 2025
digestboolean  Short-TermIndicates a digest task.
queryboolean  Short-TermRepresents a query task.