davidradl commented on code in PR #27716: URL: https://github.com/apache/flink/pull/27716#discussion_r2873327706
########## docs/content/docs/ops/management_blocklist.md: ########## @@ -0,0 +1,218 @@ +--- +title: "Management Blocklist" +weight: 9 +type: docs +--- +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> + +# Management Blocklist + +The Management Blocklist is a feature that allows cluster administrators to temporarily block problematic nodes from receiving new task allocations. This is useful for maintenance, troubleshooting, or handling nodes with performance issues without completely removing them from the cluster. Review Comment: it would be useful to give some details on how you might recognise a problematic node and why no receiving new task allocations is useful; I assume there was a scenario which this was reported for. I assume that this would be some sort of process wide issue as we are stopping new slots from being allocated. It would be useful to understand the consequences to the stream oif doing this , I assume there are side effects, like potentially increased back pressure if there are not enough other task managers available. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
