[jira] [Updated] (HDDS-427) For containers with no replica ContainerStateMap#getContainerReplicas should return empty map

2018-09-28 Thread Ajay Kumar (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ajay Kumar updated HDDS-427:

Issue Type: Bug  (was: Improvement)

> For containers with no replica ContainerStateMap#getContainerReplicas should 
> return empty map
> -
>
> Key: HDDS-427
> URL: https://issues.apache.org/jira/browse/HDDS-427
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Ajay Kumar
>Assignee: Ajay Kumar
>Priority: Major
> Attachments: HDDS-427.00.patch
>
>
> Callers of API ContainerStateMap#getContainerReplicas should be allowed to 
> decide if its violation of some condition (when there are no replicas, 
> warranting exception) instead of it being implicit to every caller. Instead 
> ContainerStateMap#getContainerReplicas should return empty map for no 
> replicas. Callers can decide if no replicas for given container is a volition 
> of business condition. Throwing exception in this API also results in a 
> subtle bug in ContainerReportHandler where exception for one container may 
> result in whole container list being skipped.



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-427) For containers with no replica ContainerStateMap#getContainerReplicas should return empty map

2018-09-10 Thread Ajay Kumar (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ajay Kumar updated HDDS-427:

Status: Open  (was: Patch Available)

> For containers with no replica ContainerStateMap#getContainerReplicas should 
> return empty map
> -
>
> Key: HDDS-427
> URL: https://issues.apache.org/jira/browse/HDDS-427
> Project: Hadoop Distributed Data Store
>  Issue Type: Improvement
>Reporter: Ajay Kumar
>Assignee: Ajay Kumar
>Priority: Major
> Attachments: HDDS-427.00.patch
>
>
> Callers of API ContainerStateMap#getContainerReplicas should be allowed to 
> decide if its violation of some condition (when there are no replicas, 
> warranting exception) instead of it being implicit to every caller. Instead 
> ContainerStateMap#getContainerReplicas should return empty map for no 
> replicas. Callers can decide if no replicas for given container is a volition 
> of business condition. Throwing exception in this API also results in a 
> subtle bug in ContainerReportHandler where exception for one container may 
> result in whole container list being skipped.



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-427) For containers with no replica ContainerStateMap#getContainerReplicas should return empty map

2018-09-10 Thread Ajay Kumar (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ajay Kumar updated HDDS-427:

Attachment: (was: HDDS-427.00.patch)

> For containers with no replica ContainerStateMap#getContainerReplicas should 
> return empty map
> -
>
> Key: HDDS-427
> URL: https://issues.apache.org/jira/browse/HDDS-427
> Project: Hadoop Distributed Data Store
>  Issue Type: Improvement
>Reporter: Ajay Kumar
>Assignee: Ajay Kumar
>Priority: Major
> Attachments: HDDS-427.00.patch
>
>
> Callers of API ContainerStateMap#getContainerReplicas should be allowed to 
> decide if its violation of some condition (when there are no replicas, 
> warranting exception) instead of it being implicit to every caller. Instead 
> ContainerStateMap#getContainerReplicas should return empty map for no 
> replicas. Callers can decide if no replicas for given container is a volition 
> of business condition. Throwing exception in this API also results in a 
> subtle bug in ContainerReportHandler where exception for one container may 
> result in whole container list being skipped.



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-427) For containers with no replica ContainerStateMap#getContainerReplicas should return empty map

2018-09-10 Thread Ajay Kumar (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ajay Kumar updated HDDS-427:

Status: Patch Available  (was: Open)

> For containers with no replica ContainerStateMap#getContainerReplicas should 
> return empty map
> -
>
> Key: HDDS-427
> URL: https://issues.apache.org/jira/browse/HDDS-427
> Project: Hadoop Distributed Data Store
>  Issue Type: Improvement
>Reporter: Ajay Kumar
>Assignee: Ajay Kumar
>Priority: Major
> Attachments: HDDS-427.00.patch
>
>
> Callers of API ContainerStateMap#getContainerReplicas should be allowed to 
> decide if its violation of some condition (when there are no replicas, 
> warranting exception) instead of it being implicit to every caller. Instead 
> ContainerStateMap#getContainerReplicas should return empty map for no 
> replicas. Callers can decide if no replicas for given container is a volition 
> of business condition. Throwing exception in this API also results in a 
> subtle bug in ContainerReportHandler where exception for one container may 
> result in whole container list being skipped.



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-427) For containers with no replica ContainerStateMap#getContainerReplicas should return empty map

2018-09-10 Thread Ajay Kumar (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ajay Kumar updated HDDS-427:

Attachment: HDDS-427.00.patch

> For containers with no replica ContainerStateMap#getContainerReplicas should 
> return empty map
> -
>
> Key: HDDS-427
> URL: https://issues.apache.org/jira/browse/HDDS-427
> Project: Hadoop Distributed Data Store
>  Issue Type: Improvement
>Reporter: Ajay Kumar
>Assignee: Ajay Kumar
>Priority: Major
> Attachments: HDDS-427.00.patch
>
>
> Callers of API ContainerStateMap#getContainerReplicas should be allowed to 
> decide if its violation of some condition (when there are no replicas, 
> warranting exception) instead of it being implicit to every caller. Instead 
> ContainerStateMap#getContainerReplicas should return empty map for no 
> replicas. Callers can decide if no replicas for given container is a volition 
> of business condition. Throwing exception in this API also results in a 
> subtle bug in ContainerReportHandler where exception for one container may 
> result in whole container list being skipped.



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-427) For containers with no replica ContainerStateMap#getContainerReplicas should return empty map

2018-09-10 Thread Ajay Kumar (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ajay Kumar updated HDDS-427:

Attachment: HDDS-427.00.patch

> For containers with no replica ContainerStateMap#getContainerReplicas should 
> return empty map
> -
>
> Key: HDDS-427
> URL: https://issues.apache.org/jira/browse/HDDS-427
> Project: Hadoop Distributed Data Store
>  Issue Type: Improvement
>Reporter: Ajay Kumar
>Assignee: Ajay Kumar
>Priority: Major
> Attachments: HDDS-427.00.patch
>
>
> Callers of API ContainerStateMap#getContainerReplicas should be allowed to 
> decide if its violation of some condition (when there are no replicas, 
> warranting exception) instead of it being implicit to every caller. Instead 
> ContainerStateMap#getContainerReplicas should return empty map for no 
> replicas. Callers can decide if no replicas for given container is a volition 
> of business condition. Throwing exception in this API also results in a 
> subtle bug in ContainerReportHandler where exception for one container may 
> result in whole container list being skipped.



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-427) For containers with no replica ContainerStateMap#getContainerReplicas should return empty map

2018-09-10 Thread Ajay Kumar (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ajay Kumar updated HDDS-427:

Description: Callers of API ContainerStateMap#getContainerReplicas should 
be allowed to decide if its violation of some condition (when there are no 
replicas, warranting exception) instead of it being implicit to every caller. 
Instead ContainerStateMap#getContainerReplicas should return empty map for no 
replicas. Callers can decide if no replicas for given container is a volition 
of business condition. Throwing exception in this API also results in a subtle 
bug in ContainerReportHandler where exception for one container may result in 
whole container list being skipped.  (was: Callers of an API 
ContainerStateMap#getContainerReplicas should be allowed to decide if its 
voilaton of some condition (warranting exception) instead of it being implicit 
to every caller. ContainerStateMap#getContainerReplicas should return empty 
map. Callers can decide if no replicas for given container is a volition of a 
business condition. Throwing exception in this API also results in a subtle bug 
in ContainerReportHandler where exception for one container may result in whole 
container list being skipped.)

> For containers with no replica ContainerStateMap#getContainerReplicas should 
> return empty map
> -
>
> Key: HDDS-427
> URL: https://issues.apache.org/jira/browse/HDDS-427
> Project: Hadoop Distributed Data Store
>  Issue Type: Improvement
>Reporter: Ajay Kumar
>Assignee: Ajay Kumar
>Priority: Major
>
> Callers of API ContainerStateMap#getContainerReplicas should be allowed to 
> decide if its violation of some condition (when there are no replicas, 
> warranting exception) instead of it being implicit to every caller. Instead 
> ContainerStateMap#getContainerReplicas should return empty map for no 
> replicas. Callers can decide if no replicas for given container is a volition 
> of business condition. Throwing exception in this API also results in a 
> subtle bug in ContainerReportHandler where exception for one container may 
> result in whole container list being skipped.



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org