[
https://issues.apache.org/jira/browse/HDFS-17256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liying updated HDFS-17256:
--------------------------
Environment: (was: In general, we do not need to set isolation limits
for all namespaces in cluster. For example, we only need to set the isolation
limits for the problem namespaces to avoid affecting other namespaces when some
namespaces occur errors. If we set isolation limits for all namespaces in
cluster, it brings many risks by itself as it is very difficult to confirm the
specific parameters. Instead，The result is increasing request latency for
other namespaces. Let's talk about a specific scenario:
when ns1 service is unavailable as some bugs，we turn on isolation-related
switches dynamically to support the abnormal ns isolation in router ， and set
the handler number of abnormal ns as low as possible to avoid affecting other
namespaces.)
> add the individual namespaces isolation mode for router to avoid affecting
> other namespaces
> -------------------------------------------------------------------------------------------
>
> Key: HDFS-17256
> URL: https://issues.apache.org/jira/browse/HDFS-17256
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: rbf
> Affects Versions: 3.2.1
> Reporter: liying
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
