Hi Daryn,
This is an interesting and valid point to consider different implications
for security.
The purpose of the alignment context is to allow clients and servers sync
on their global state, so that when clients switch between ANN/SBN or
between SBNs, the reads are always consistent. One reas
Hi Yongjun,
Automatic failover sure needs to be fixed (see HDFS-14130 and HDFS-13182).
Along with all other outstanding issues. We plan to continue this on trunk.
The feature is usable now without this issues (see HDFS-14067).
And we would like to get it in, so that people could have early access,
Hi Daryn,
I have just started reading the patch. Hence my apologies if my question has a
response somewhere hidden in the patch.
Are you concerned that FSEditLock is taken in GlobalStateIdContext on Server
side, and worried that a malicious or stupid client would
cause this lock to be held up
-1 pending additional info. After a cursory scan, I have serious concerns
regarding the design. This seems like a feature that should have been
purely implemented in hdfs w/o touching the common IPC layer.
The biggest issue in the alignment context. It's purpose appears to be for
allowing handl
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/979/
[Dec 5, 2018 8:56:10 PM] (eyang) YARN-9057. Removed third party class bundle
from CSI jar file.
[Dec 5, 2018 10:00:56 PM] (eyang) YARN-9071. Improved status update for
reinitialized containers.
Roman Leventov created HADOOP-15985:
---
Summary: LightWeightGSet.computeCapacity() doesn't correctly
account for CompressedOops
Key: HADOOP-15985
URL: https://issues.apache.org/jira/browse/HADOOP-15985
