hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-264) WritableFactory has no permissions to create DatanodeRegistration
Date Thu, 01 Jun 2006 01:40:30 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-264?page=all ]

Konstantin Shvachko updated HADOOP-264:

    Attachment: PublicDatanodeRegistration.patch

I agree with Owen that DatanodeRegistration as well as other classes passed through RPC should
be public.
The counter-patch :-) with only one word added is attached.
Since it is related to HADOOP-124 making some classes non-public,
I would return public status to the exceptions as well.
Just speculating: if RPC would have to convert RemoteException to the real
exceptions like LeaseExpiredException then it would crash for the same reason.
We do not have that mechanism (for converting exceptions) yet, but one day we will.

> WritableFactory has no permissions to create DatanodeRegistration
> -----------------------------------------------------------------
>          Key: HADOOP-264
>          URL: http://issues.apache.org/jira/browse/HADOOP-264
>      Project: Hadoop
>         Type: Bug

>   Components: dfs
>     Versions: 0.3
>     Reporter: Owen O'Malley
>     Assignee: Owen O'Malley
>     Priority: Blocker
>      Fix For: 0.3
>  Attachments: PublicDatanodeRegistration.patch, fix-datanode-registration-perm.patch
> The datanode can not come up because the DatanodeRegistration is package local and the
factory registration doesn't happen.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message