HDDS-4567: SCMContext Phase 1 - Raft Related Info #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nce states. Contributed by Stephen O'Donnell.
…ecommission and maintenance commands to be sent from the CLI and update the node status in a skeleton decommission manager
Some tests are failing: org.apache.hadoop.hdds.scm.block.TestBlockManager org.apache.hadoop.ozone.om.ratis.TestOzoneManagerDoubleBufferWithOMResponse
…/asf/hadoop-ozone into HDDS-1880-Decom
Signed-off-by: Anu Engineer <[email protected]>
…ers and complete the admin workflow accordingly Closes apache#309
…inMontor interface (apache#355)
… maintenance states
…sion and maintenance states" This reverts commit 5b228c0.
…commission and Maintenance
… maintenance states apache#433
apache#1647) * HDDS-4265. Refactor OzoneQuota to make it easy to support more quota type * fix checkstyle * Fix checkstyle * fix checkstyle again * Fix space and indentation * fix space issue again
…es leader/follower. (apache#1615)
…#1691) * HDDS-4579. Add acceptance test for Ozone Client Key Validator * trigger new CI check * trigger new CI check * trigger new CI check
…ate and delete bucket (apache#1445) * HDDS-4272. Volume namespace: add usedNamesapce and update it when create and delete bucket * fixup! comments addressed. * fjxup! address comments * trigger new CI check * fixup! fix UT * fixup! fix CI
* HDDS-4581. Cleanup usage of volumeArgs in KeyRequests.
…w in processing reports (apache#1601) * HDDS-4404. Datanode can go OOM when a Recon or SCM Server is very slow in processing reports. Change-Id: Idf6394d0bde2fb1c9fe99a96c49fa28677e0e527 * Checkstyle. Change-Id: I6c4729634905bf6bba5bb6483c393d3c7511a78e * Add mock-maker-inline so UT can mock final classes. Change-Id: I63470510ed2089438f08f4d3cea321c1b5f01c3c * Remove throw exception in addReport. Change-Id: Id3ff6222ed279568d32876afc0a6a5ee1316c926 * Fix existing UT TestStateContext#testReportAPIs. Change-Id: I25020b4411f4163a2ec134431793bfe663e5f6bf * Remove unused imports. Change-Id: I2dc93c42fc7468b37d41a179ca047ee385fc8896 * Work around mockito bug in UT TestCreatePipelineCommandHandler: caused by adding mock-maker-inline. Change-Id: I0f21c508af1f7b36d7632aaa3b9173a17056f211 * Add UT testContainerNodePipelineReportAPIs. Change-Id: I8d67a1b6e2d9043fb1479e2547d2e690932f7985 * Clean up. Change-Id: Iaec544ba6fb211d0d71fe03b26b0fc70199dc882 * @VisibleForTesting for get container/node/pipeline reports as they are only used in UT, at least at the moment. Change-Id: I72070fde8df220ecebf2fb6d1015d19f65cee11e * - Renamed `reports` to `incrementalReportsQueue` to better reflect the functionality of the map. - Added `acceptedIncrementalReportTypeSet` for rigorous report type checking. - `StateContext#addReport` now explicitly throws, instead of hiding any possible NPEs. Rationale: As I think again, those reports are all internally generated rather than dependent on direct user input. It's better to catch any problem early (if any). - `StateContext#addReport` also strictly checks for report type now. This intends to force any future additions of report types to be explicitly allowed. Only 5 report types (names) are expected: ``` hadoop.hdds.NodeReportProto hadoop.hdds.ContainerReportsProto hadoop.hdds.IncrementalContainerReportProto hadoop.hdds.CommandStatusReportsProto hadoop.hdds.PipelineReportsProto ``` - `StateContext#putBackReports` now checks ALL reports in the list to be put back. I'd expect the list to be small. And since the logic is run on each DataNode, it shouldn't become a performance bottleneck. Also added debug logging just in case we need to diagnose it in the future. - Added new UT `testPutBackReports` and `testReportQueueWithAddReports` to check that `putBackReports` and `getReports` behaves. Change-Id: I48aca3d4a422d52532b39c9462a30519c9cbe0eb * Make containerReports, nodeReport, pipelineReports atomic and final. Change-Id: I44aba0ff093fa0ff5f9a35a74ff4126d9c73dd7b * Checkstyle. Change-Id: I545ca8c636b8bbd1239a936603b6efcbfbd10b88 * Clean up. Change-Id: I5cdc38a297cf3d91bad8335eb36f2ba6b2009c10 * Remove assertion in putBackReports as requestBuilder might include Container/Node/Pipeline reports. Thanks Aravindan. Change-Id: Ic39f53de8bb91a179bd5dc3301aa89ffecf5c076 * Empty commit to retrigger CI. Change-Id: I46fb65ce2c81cb607dd10a9ee829d829ec7a8cfc * Empty commit to retrigger CI. Change-Id: I9d3b5ce0b81d457344ecd6b4ad6e141169bd89d3 * Retrigger. Change-Id: I4e9dace08152e21c2bb5da564487d776a84c4ade * Allow null as input to StateContext#addReport() as this blocked UT TestStorageContainerManager#testBlockDeletionTransactions. Change-Id: I16c8bfcfbd619a23241ea6dda9b95265714984bb * Retrigger CI Change-Id: I64203ebbaeebdb4c598bb8dad578579c82bf604b * trigger new CI check Co-authored-by: Doroszlai, Attila <[email protected]>
* HDDS-4582 Update QUOTA_IN_COUNTS to quota in namespace
GlenGeng-awx
force-pushed
the
HDDS-4575
branch
from
8a84b03 to
5d9b029
Compare
GlenGeng-awx
force-pushed
the
HDDS-4567
branch
from
5444fdd to
1b7b505
Compare
added 2 commits
December 17, 2020 15:15
…eOverReplicatedContainer(). (apache#1700)
GlenGeng-awx
force-pushed
the
HDDS-4567
branch
3 times, most recently
from
2128280 to
926e4e7
Compare
GlenGeng-awx
force-pushed
the
HDDS-4567
branch
from
926e4e7 to
75ba45d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
What is the link to the Apache JIRA
(Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HDDS-XXXX. Fix a typo in YYY.)
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)