The
setMinHostAlivePercentageToEnableClusterRebalancing()
GraphQL mutation is used to set the percentage of all hosts relevant
to a particular cluster rebalance operation that need to be alive
before we allow the system to execute automatically the operation to
the supplied value. Cluster rebalance operations currently include
reassigning digest work, and moving existing segments to balance
disk usage.
Below is the syntax for
setMinHostAlivePercentageToEnableClusterRebalancing() :
setMinHostAlivePercentageToEnableClusterRebalancing(
minHostAlivePercentageToEnableClusterRebalancing : integer!
) : integer!
Below is an example of how this mutation field might be used:
Show:
Raw Mac OS or Linux (curl) Mac OS or Linux (curl) One-line Windows Cmd and curl Windows Powershell and curl Perl Python Node.js
Raw mutation {
setMinHostAlivePercentageToEnableClusterRebalancing(
minHostAlivePercentageToEnableClusterRebalancing : 50
)
}
Mac OS or Linux (curl) curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d @- << EOF
{"query" : "mutation {
setMinHostAlivePercentageToEnableClusterRebalancing(
minHostAlivePercentageToEnableClusterRebalancing: 50
)
}"
}
EOF
Mac OS or Linux (curl) One-line curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d @- << EOF
{"query" : "mutation {
setMinHostAlivePercentageToEnableClusterRebalancing(
minHostAlivePercentageToEnableClusterRebalancing: 50
)
}"
}
EOF
Windows Cmd and curl curl -v -X POST $YOUR_LOGSCALE_URL/graphql ^
-H "Authorization: Bearer $TOKEN" ^
-H "Content-Type: application/json" ^
-d @'{"query" : "mutation { ^
setMinHostAlivePercentageToEnableClusterRebalancing( ^
minHostAlivePercentageToEnableClusterRebalancing: 50 ^
) ^
}" ^
} '
Windows Powershell and curl curl.exe -X POST
-H "Authorization: Bearer $TOKEN "
-H "Content-Type: application/json"
-d '{"query" : "mutation {
setMinHostAlivePercentageToEnableClusterRebalancing(
minHostAlivePercentageToEnableClusterRebalancing: 50
)
}"
}'
"$YOUR_LOGSCALE_URL /graphql"
Perl
use HTTP::Request;
use LWP;
my $INGEST_TOKEN = "TOKEN" ;
my $uri = '$YOUR_LOGSCALE_URL/graphql' ;
my $json = '{"query" : "mutation {
setMinHostAlivePercentageToEnableClusterRebalancing(
minHostAlivePercentageToEnableClusterRebalancing: 50
)
}"
}' ;
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
import requests
url = '$YOUR_LOGSCALE_URL/graphql'
mydata = r'''{"query" : "mutation {
setMinHostAlivePercentageToEnableClusterRebalancing(
minHostAlivePercentageToEnableClusterRebalancing: 50
)
}"
}'''
resp = requests.post(url,
data = mydata,
headers = {
"Authorization" : "Bearer $TOKEN" ,
"Content-Type" : "application/json"
}
)
print (resp.text)
Node.js const https = require ('https' );
const data = JSON .stringify (
{"query" : "mutation {
setMinHostAlivePercentageToEnableClusterRebalancing(
minHostAlivePercentageToEnableClusterRebalancing: 50
)
}"
}
);
const options = {
hostname : '$YOUR_LOGSCALE_URL/graphql' ,
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 Show:
Success (HTTP Response Code 200 OK)
Success (HTTP Response Code 200 OK) {
"data" : {
"setMinHostAlivePercentageToEnableClusterRebalancing" : 50
}
}
This mutation field has no special datatypes. It uses integer for
both the input and the return datatype.
For the given data, enter the percentage of all hosts relevant to
a particular cluster rebalance operation that need to be alive
before we allow the system to automatically execute the operation.
Cluster rebalance operations currently include reassigning digest
work, and moving existing segments to balance disk usage. Must be
between 0 and 100, both inclusive.