|
Блокировка IDS 11.5 при выполнении КТ с асинхронной HDR.
|
|||
---|---|---|---|
#18+
victor16Если уж речь зашла о команде onstat -P, то есть три вещи, на которые надо обратить внимание в выводе этой команды. Почти готовый FAQ типа "Какую пользу можно извлечь из вывода onstat -P" ? Будет время, надо будет оформить.... ... |
|||
:
Нравится:
Не нравится:
|
|||
17.02.2010, 13:37 |
|
Блокировка IDS 11.5 при выполнении КТ с асинхронной HDR.
|
|||
---|---|---|---|
#18+
Дабы осталось в общественном разуме: What's New in IDS 11.50 - January 2010 V2 On very logging active HDR primaries, checkpoint performance on the secondary can have a negative performance impact on the primary. If while the checkpoint is performed on the secondary, all HDR buffer resources fill, the secondary is then unable to receive more HDR buffers from the primary. At that point, there are also limited HDR buffers available on the primary, and when they fill, all logging activity on the primary halts until the checkpoint can complete on the secondary. With log staging configured on the secondary, while the checkpoint is being performed, the HDR secondary will be able to continue to receive log data from the primary. This should prevent the primary from blocking logging activity because of no available HDR buffers. To enable Log Staging you need to set 2 parameters in the ONCONFIG: LOG_STAGING_DIR LOG_INDEX_BUILDS This feature was added in 11.50.xC6: Documented in Administrator's Guide, Using High-Availability Data Replication chapter, section on “Prevent Blocking Checkpoints on HDR Servers” ... |
|||
:
Нравится:
Не нравится:
|
|||
15.03.2010, 17:00 |
|
|
start [/forum/topic.php?fid=44&gotonew=1&tid=1607621]: |
0ms |
get settings: |
9ms |
get forum list: |
13ms |
check forum access: |
4ms |
check topic access: |
4ms |
track hit: |
47ms |
get topic data: |
13ms |
get first new msg: |
8ms |
get forum data: |
3ms |
get page messages: |
50ms |
get tp. blocked users: |
2ms |
others: | 11ms |
total: | 164ms |
0 / 0 |