pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Dai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIG-2034) Pig client uses fs.default.name as provided from the JobTracker instead of local value
Date Thu, 05 May 2011 01:44:03 GMT

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

Daniel Dai commented on PIG-2034:
---------------------------------

I would say yes. Client side use server side configuration, that seems counter intuitive.

> Pig client uses fs.default.name as provided from the JobTracker instead of local value
> --------------------------------------------------------------------------------------
>
>                 Key: PIG-2034
>                 URL: https://issues.apache.org/jira/browse/PIG-2034
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Bill Graham
>         Attachments: pig_1304465896181.log
>
>
> When submitting a Pig job, the client uses the {{fs.default.name}} supplied to it by
the JobTracker (via core-site.xml on the master typically) during the staging phase. After
that, the client then uses the {{fs.default.name}} from it's local configs. This seems like
a bug to me. Expected behavior would be to always use the local value.
> I found this bug when the server configs were set to not use a FQDN for {{fs.default.name}}.
This caused the client to fail because it didn't have the same default DNS domain. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message