[jira] [Created] (HDFS-2629) Implement protobuf service for InterDatanodeProtocol

2011-12-04 Thread Suresh Srinivas (Created) (JIRA)
Implement protobuf service for InterDatanodeProtocol


 Key: HDFS-2629
 URL: https://issues.apache.org/jira/browse/HDFS-2629
 Project: Hadoop HDFS
  Issue Type: New Feature
  Components: data-node
Reporter: Suresh Srinivas
 Fix For: 0.24.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (HDFS-2626) HA: BPOfferService.verifyAndSetNamespaceInfo needs to be synchronized

2011-12-04 Thread Todd Lipcon (Resolved) (JIRA)

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

Todd Lipcon resolved HDFS-2626.
---

   Resolution: Fixed
Fix Version/s: HA branch (HDFS-1623)
 Hadoop Flags: Reviewed

Committed to branch, thanks for the review.

> HA: BPOfferService.verifyAndSetNamespaceInfo needs to be synchronized
> -
>
> Key: HDFS-2626
> URL: https://issues.apache.org/jira/browse/HDFS-2626
> Project: Hadoop HDFS
>  Issue Type: Sub-task
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
> Fix For: HA branch (HDFS-1623)
>
> Attachments: hdfs-2626.txt
>
>
> When starting an HA blockpool with both namenodes up, I often see an NPE, 
> referenced by one of the TODOs. The issue is the following interleaving:
> - first BPActor registers, and sets bpNSInfo in BPOfferService. It then 
> proceeds to initFsDataset which takes a little bit of time
> - second BPActor registers, and sees bpNSInfo is non-null, then proceeds to 
> heartbeat loop. Meanwhile BPActor 1 is still initting FSDataset
> - second BPActor gets an NPE on first heartbeat since fsdataset is still null.
> We just need to synchronize that function to fix the NPE.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (HDFS-2624) HA: ConfiguredFailoverProxyProvider doesn't correctly stop ProtocolTranslators

2011-12-04 Thread Todd Lipcon (Resolved) (JIRA)

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

Todd Lipcon resolved HDFS-2624.
---

  Resolution: Fixed
Hadoop Flags: Reviewed

Committed to branch, thx for reviews.

> HA: ConfiguredFailoverProxyProvider doesn't correctly stop ProtocolTranslators
> --
>
> Key: HDFS-2624
> URL: https://issues.apache.org/jira/browse/HDFS-2624
> Project: Hadoop HDFS
>  Issue Type: Sub-task
>Affects Versions: HA branch (HDFS-1623)
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
> Fix For: HA branch (HDFS-1623)
>
> Attachments: hdfs-2624.txt
>
>
> In the tip of branch, the direct proxies to the NN have been replaced by 
> ProtocolTranslator implementations. But, the proxy provider still calls 
> RPC.stopProxy, which generates a warning and doesn't actually stop the proxy. 
> We need to check if the protocol implementation is a Closeable and call 
> close() instead in that case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (HDFS-2625) HA: TestDfsOverAvroRpc failing after introduction of HeartbeatResponse type

2011-12-04 Thread Todd Lipcon (Resolved) (JIRA)

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

Todd Lipcon resolved HDFS-2625.
---

   Resolution: Fixed
Fix Version/s: HA branch (HDFS-1623)
 Hadoop Flags: Reviewed

Committed to branch, thx for the review.

> HA: TestDfsOverAvroRpc failing after introduction of HeartbeatResponse type
> ---
>
> Key: HDFS-2625
> URL: https://issues.apache.org/jira/browse/HDFS-2625
> Project: Hadoop HDFS
>  Issue Type: Sub-task
>  Components: ha, test
>Affects Versions: HA branch (HDFS-1623)
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
>Priority: Minor
> Fix For: HA branch (HDFS-1623)
>
> Attachments: hdfs-2625.txt
>
>
> TestDfsOverAvroRpc is failing after HDFS-2616. The issue seems to be that we 
> sometimes fill in the "commands" list in HeartbeatResponse with null to 
> indicate no commands. This makes avro barf with a cryptic message about 
> unions of nulls of unions of arrays of nulls or something.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira