On 08/22/15 16:35, Grigory Shamov wrote:
> Hi All,
>
> We have updated Lustre version from 1.8 to 2.x and now I probably want to
> reinstall/update Robinhood accordingly.
>
> Do I have to purge and re-create existing MySQL databases for that, or
> just updating client RPM will do?
The primary key of robinhood tables in not the same for Lustre 1.x and 
Lustre 2.x (now uses lustre fid)
so you have to drop the DB and run a full scan.

>   The update would be from Robinhood 2.5.4
> to the current 2.5.5-2. As of now the plan is to do full scan first,
> before experimenting with Lustre change logs.
I suggest you register a changelog reader on MDT before running this 
initial scan
so you won't have to run another full scan to synchronize the DB when 
you'll want to enable robinhood changelog reader.

To speed up the initial scan:
* disable user_acct/group_acct parameters for the time of the first scan
* Try these Lustre tuning on robinhood host:
     lctl set_param llite.*.statahead_max=4
     lctl set_param ldlm.namespaces.*.lru_size=100
     lctl set_param ldlm.namespaces.*.lru_max_age=1200
     lctl set_param mdc.*.max_rpcs_in_flight=64
     sysctl -w lnet.debug=0

Regards

>
> Thank you very much!
>


------------------------------------------------------------------------------
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support

Reply via email to