giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maja Kabiljo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-315) giraph-site.xml isn't read on time
Date Tue, 11 Sep 2012 12:44:08 GMT

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

Maja Kabiljo commented on GIRAPH-315:
-------------------------------------

Yes, it is happening, but just in tests.

Here are a few things I noticed while investigating this, maybe they'll make more sense to
you since you worked a lot with Configuration already.

For example while in BspCase.setupConfiguration confgurations from other files (i.e. core-site.xml,
mapred-default.xml...) are not visible either, I guess it looks for them in different folder.


On master static block of GiraphJob gets called some steps after MasterThread.run is called
(this happens also when running benchmarks and examples). But it seems like when we execute
"hadoop jar ..." it gets called somewhere before also, not sure where. 

In tests config object has the same resources as the one we get with new Configuration(),
which is otherwise not the case.
                
> giraph-site.xml isn't read on time
> ----------------------------------
>
>                 Key: GIRAPH-315
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-315
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Maja Kabiljo
>            Assignee: Maja Kabiljo
>            Priority: Trivial
>         Attachments: GIRAPH-315.patch
>
>
> While running some tests I noticed that on the master I get different values of some
configuration parameters in the beginning of the execution than later on. It turned out that
giraph-site.xml gets added as default resource a bit later than it should.
> This only happens when running tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message