On 22 August 2011 18:06, Govind Songara <[log in to unmask]> wrote:
> Hi All,
>
> If I trust ..
> No srm failures,no high number of TIME_WAIT, no high load, no FTS
> performance issue for last 4-5 days.
> then we seems to have resolved the long lasting dpm problem.
>
> The main root cause was mysql DB engine, DPM only support InnoDB, but in our
> case it was MyISAM. If you install mysq-server then MyISAM is default
> engine. So anyone can fall in this situations if they have not take any
> actions by setting a variable (default-storage-engine=innodb) in my.cnf or
> something else.
> - did not find any instruction on dpm install where it mentioned InnoDB
> engine should be used. I thought schema should be handling this.
It does.
/opt/lcg/share/DPM/create_dpns_tables_mysql.sql
is the script sourced by YAIM when configuring DPM with a mysql
backend (it is called by the function config_DPM_mysql). In my copy of
it, at least, it explicitly sets the DPM databases and tables to use
InnoDB.
Sam
|