[Swift-devel] Re: coaster features

[Zhao Zhang]

Hi, All

Mihael Hategan wrote:
> On Thu, 2009-05-14 at 11:36 -0500, Zhao Zhang wrote:
>   
>>> I'm not sure how you know it's working if you don't know what it's
>>> supposed to do.
>>>   
>>>       
>> Yes, there is a test case in Ben's test suite using the 
>> coasterInternalIP variable. Things I know is that the test returned 
>> successful.
>>     
>
> Did you try to remove that parameter and see if there is a difference?
>
>   
>>> Without this, workers use the external IP (the one the service is
>>> started with) to contact the service. With it, one can force the workers
>>> to contact a specific IP after starting. This is needed if the worker
>>> nodes don't generally have access to the outside of the cluster.
>>>
>>> This has nothing to do with notification or status files. If this
>>> setting is required (due to the network configuration of the cluster)
>>> and it is not specified, the coasters won't work at all.
>>>
>>>   
>>>       
>>>> 4) coasterDataProvider
>>>>     This is working now.
>>>>     
>>>>         
>>> I don't know what that is.
>>>   
>>>       
>> This is the "<filesystem provider="coaster" url="gt2://grid.myhost.org" 
>> />" from http://www.ci.uchicago.edu/swift/guides/userguide/coasters.php.
>>     
>
> Right. The coaster fs provider. Glen found some data corruption with it
> when transferring files larger than a few KB. So it's only somewhat
> working.
>   
Has this feature been fixed? I found it again in my data movement test 
on OSG site.

zhao
>
>