On 24 May 2011 17:39, Ewan MacMahon <[log in to unmask]> wrote:
>> -----Original Message-----
>> From: Sam Skipsey [mailto:[log in to unmask]]
>> Sent: 24 May 2011 16:34
>> To: Ewan MacMahon
>>
>> And this kind of horrible complication is why I was holding out for a
>> proper targeted dpm-replicate command in the API so I could make a proper
>> rebalancing script (the existing one basically just juggles RDONLY and
>> other filesystem statuses while doing drains of the fullest filesystems in
>> the system).
>>
> I'm sure there's a good reason for this, but why do we actually
> need support within DPM for this? Can't we just move the data
> (with rfio/scp/something else), then change the database (directly
> with mysql) to point to the new location; job done?
>
If you shut DPM down before you make the change and bring it up again
when you've made it, that'd probably work. DPM holds copies of stuff
in memory, which the api methods also adjust, which is why I'd like it
to be supported in that level.
Sam
> Ewan
>
|