[ 
https://issues.apache.org/jira/browse/HDDS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595189#comment-16595189
 ] 

genericqa commented on HDDS-343:
--------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
31s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 23m 
 1s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
27s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
18s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green}  0m 
28s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
11m 52s{color} | {color:green} branch has no errors when building and testing 
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
38s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
24s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
20s{color} | {color:red} server-scm in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red}  0m 
19s{color} | {color:red} server-scm in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red}  0m 19s{color} 
| {color:red} server-scm in the patch failed. {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
14s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} mvnsite {color} | {color:red}  0m 
20s{color} | {color:red} server-scm in the patch failed. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 
12m 32s{color} | {color:green} patch has no errors when building and testing 
our client artifacts. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  0m 
19s{color} | {color:red} server-scm in the patch failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
19s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}  0m 20s{color} 
| {color:red} server-scm in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
25s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 53m  7s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:ba1ab08 |
| JIRA Issue | HDDS-343 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12937452/HDDS-343.005.patch |
| Optional Tests |  asflicense  compile  javac  javadoc  mvninstall  mvnsite  
unit  shadedclient  findbugs  checkstyle  |
| uname | Linux e544ac9e448e 3.13.0-153-generic #203-Ubuntu SMP Thu Jun 14 
08:52:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / 75691ad |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC1 |
| mvninstall | 
https://builds.apache.org/job/PreCommit-HDDS-Build/877/artifact/out/patch-mvninstall-hadoop-hdds_server-scm.txt
 |
| compile | 
https://builds.apache.org/job/PreCommit-HDDS-Build/877/artifact/out/patch-compile-hadoop-hdds_server-scm.txt
 |
| javac | 
https://builds.apache.org/job/PreCommit-HDDS-Build/877/artifact/out/patch-compile-hadoop-hdds_server-scm.txt
 |
| mvnsite | 
https://builds.apache.org/job/PreCommit-HDDS-Build/877/artifact/out/patch-mvnsite-hadoop-hdds_server-scm.txt
 |
| findbugs | 
https://builds.apache.org/job/PreCommit-HDDS-Build/877/artifact/out/patch-findbugs-hadoop-hdds_server-scm.txt
 |
| unit | 
https://builds.apache.org/job/PreCommit-HDDS-Build/877/artifact/out/patch-unit-hadoop-hdds_server-scm.txt
 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HDDS-Build/877/testReport/ |
| Max. process+thread count | 302 (vs. ulimit of 10000) |
| modules | C: hadoop-hdds/server-scm U: hadoop-hdds/server-scm |
| Console output | 
https://builds.apache.org/job/PreCommit-HDDS-Build/877/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Containers are stuck in closing state in scm
> --------------------------------------------
>
>                 Key: HDDS-343
>                 URL: https://issues.apache.org/jira/browse/HDDS-343
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: SCM
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Blocker
>             Fix For: 0.2.1
>
>         Attachments: HDDS-343.001.patch, HDDS-343.002.patch, 
> HDDS-343.003.patch, HDDS-343.004.patch, HDDS-343.005.patch
>
>
> Containers could not been closed currently.
> The datanode is closing the containers and sending the CLOSED state in the 
> container report but SCM doesn't register that the state is closed and 
> sending the close command again and again.
> I think the ContainerMapping.processContainerReport should be improved.
> {code}
> scm_1           | --> RPC message request: SCMHeartbeatRequestProto from 
> 172.25.0.2:33912
> scm_1           | datanodeDetails {
> scm_1           |   uuid: "9c8f80bd-9424-4d74-99ef-a2bd58e66d7f"
> scm_1           |   ipAddress: "172.25.0.2"
> scm_1           |   hostName: "365fd1f44f0b"
> scm_1           |   ports {
> scm_1           |     name: "STANDALONE"
> scm_1           |     value: 9859
> scm_1           |   }
> scm_1           |   ports {
> scm_1           |     name: "RATIS"
> scm_1           |     value: 9858
> scm_1           |   }
> scm_1           |   ports {
> scm_1           |     name: "REST"
> scm_1           |     value: 9880
> scm_1           |   }
> scm_1           | }
> scm_1           | nodeReport {
> scm_1           |   storageReport {
> scm_1           |     storageUuid: "DS-61e76107-85c5-437a-95a7-aeb8b3e7827f"
> scm_1           |     storageLocation: "/tmp/hadoop-hadoop/dfs/data"
> scm_1           |     capacity: 491630870528
> scm_1           |     scmUsed: 2708828160
> scm_1           |     remaining: 24263614464
> scm_1           |     storageType: DISK
> scm_1           |     failed: false
> scm_1           |   }
> scm_1           | }
> scm_1           | containerReport {
> scm_1           |   reports {
> scm_1           |     containerID: 1
> scm_1           |     used: 1061158912
> scm_1           |     readCount: 0
> scm_1           |     writeCount: 64
> scm_1           |     readBytes: 0
> scm_1           |     writeBytes: 1061158912
> scm_1           |     state: CLOSED
> scm_1           |   }
> scm_1           |   reports {
> scm_1           |     containerID: 2
> scm_1           |     used: 1048576000
> scm_1           |     readCount: 0
> scm_1           |     writeCount: 64
> scm_1           |     readBytes: 0
> scm_1           |     writeBytes: 1048576000
> scm_1           |     state: CLOSED
> scm_1           |   }
> scm_1           |   reports {
> scm_1           |     containerID: 3
> scm_1           |     used: 511705088
> scm_1           |     readCount: 0
> scm_1           |     writeCount: 32
> scm_1           |     readBytes: 0
> scm_1           |     writeBytes: 511705088
> scm_1           |     state: OPEN
> scm_1           |   }
> scm_1           | }
> scm_1           | commandStatusReport {
> scm_1           | }
> scm_1           | containerActions {
> scm_1           |   containerActions {
> scm_1           |     containerID: 1
> scm_1           |     action: CLOSE
> scm_1           |     reason: CONTAINER_FULL
> scm_1           |   }
> scm_1           |   containerActions {
> scm_1           |     containerID: 2
> scm_1           |     action: CLOSE
> scm_1           |     reason: CONTAINER_FULL
> scm_1           |   }
> scm_1           | }
> scm_1           | 
> scm_1           | --> RPC message response: SCMHeartbeatRequestProto to 
> 172.25.0.2:33912
> scm_1           | datanodeUUID: "9c8f80bd-9424-4d74-99ef-a2bd58e66d7f"
> scm_1           | 
> scm_1           | 2018-08-08 16:22:51 INFO  CloseContainerEventHandler:56 - 
> Close container Event triggered for container : 1
> scm_1           | 2018-08-08 16:22:51 INFO  CloseContainerEventHandler:105 - 
> container with id : 1 is in CLOSING state and need not be closed.
> scm_1           | 2018-08-08 16:22:51 INFO  CloseContainerEventHandler:56 - 
> Close container Event triggered for container : 2
> scm_1           | 2018-08-08 16:22:51 INFO  CloseContainerEventHandler:105 - 
> container with id : 2 is in CLOSING state and need not be closed.
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to