Introduction to Project atomic (CentOS Dojo Bangalore)Lalatendu Mohanty
?
The talk was given in CentOS Dojo Bangalore on 29th April 2015
http://wiki.centos.org/Events/Dojo/Bangalore2015
This slides contains introduction to Project Atomic and CentOS Atomic SIG.
This document summarizes benchmarks of MySQL multi-thread slave performance using different numbers of slave_parallel_workers threads on Oracle Cloud MySQL instances. It finds that using 16 threads provides the best performance, processing queries faster and keeping the slave less behind the master compared to lower thread counts. CPU usage is also lower with 16 threads even though more threads are used.
The document discusses Linux memory management, describing how physical memory is divided into page frames and virtual memory allows processes to have a virtual view of memory mapped to physical memory using page tables, and covers topics like memory overcommit, page cache, swap space, and tools for monitoring memory usage.
IoT Devices Compliant with JC-STAR Using Linux as a Container OSTomohiro Saneyoshi
?
Security requirements for IoT devices are becoming more defined, as seen with the EU Cyber Resilience Act and Japan’s JC-STAR.
It's common for IoT devices to run Linux as their operating system. However, adopting general-purpose Linux distributions like Ubuntu or Debian, or Yocto-based Linux, presents certain difficulties. This article outlines those difficulties.
It also, it highlights the security benefits of using a Linux-based container OS and explains how to adopt it with JC-STAR, using the "Armadillo Base OS" as an example.
Feb.25.2025@JAWS-UG IoT
16. ? NoOfFragmentLogFiles(デフォルト16)
? Redoログのファイル数。
? FragmentLogFileSize(デフォルト16MB)
? Redoログ1つのファイルサイズ
? デフォルトの場合 NoOfFragmentLogFiles * 4 *
FragmentLogFileSizeで1024MB
? The default parameter value is 16, which by default means 16
sets of 4 16MB files for a total of 1024MB)
20. 障害1
? SQLノードのエラーログに以下内容が出力
? [ERROR] /usr/local/mysql/bin/mysqld: Got temporary error 245 'Too many
active scans' from NDBCLUSTER
? 対応
? そもそも受けきれないのならフロントのWeb(Apache)のMaxClientsを下
げる(一時しのぎ)。
? TransactionDeadlockDetectionTimeoutをリトライ処理しっかりしてるな
ら小さくする
? クエリの見直し
21. 障害2
? データノードのログに以下内容が出力
? Signal lost, out of long signal memory, please increase
LongMessageBuffer (Resource configuration error)
? 対応
? LongMessageBufferを増やす。
? 使用していたバージョンではデフォルトが4MBだった
? This parameter seldom needs to be changed from the default.
? 7.3.5から64MBがデフォルトに(#^ω^)ビキビキ
22. 障害3?
? 仮想環境のndbd 3 x 2ノードグループをndbmtdの3 x 1ノ
ードグループへ変更する際に発生。
? 良くない事に時間がなく、ノードグループ数が変わる場
合にstart backupで取れるバックアップデータを使用出
来るか検証出来なかった。そのためmysqldumpしてリス
トアを試みました
24. 障害3?
? マニュアルより
? All the write operations in the cluster are added together. Setting
TimeBetweenLocalCheckpoints to 6 or less means that local
checkpoints will be executed continuously without pause,
independent of the cluster's workload.
? TimeBetweenLocalCheckpointsを6以下にしてリストア
して成功
? しかしndbmtdの再起動が発生したため大きく時間ロス。
25. 障害4
? デイリーのcronのタイミングでndbmtdが落ちる
? 出力メッセージ
INFO -- Internal program error (failed ndbrequire)
INFO -- DBTC (Line: 7783) 0x00000002
INFO -- Error handler shutting down system
INFO -- Error handler shutdown completed - exiting
ALERT -- Node 20: Forced node shutdown completed. Caused by
error 2341: 'Internal program error (failed ndbrequire)(Internal error, programming error or
missing error message, please report a bug). Temporary error, restart node'.
30. データノード
? DataMemory, IndexMemoryの使用率監視
? 管理ノード(ndb_mgmd)で定期的にチェック
ndb_mgm> all report memoryusage;
Connected to Management Server at: localhost:1186
Node 1: Data usage is 30%(177824 32K pages of total 589824)
Node 1: Index usage is 11%(44203 8K pages of total 393344)
Node 2: Data usage is 30%(177824 32K pages of total 589824)
Node 2: Index usage is 11%(44203 8K pages of total 393344)
Node 3: Data usage is 30%(177894 32K pages of total 589824)
Node 3: Index usage is 11%(44313 8K pages of total 393344)
Node 4: Data usage is 30%(177894 32K pages of total 589824)
Node 4: Index usage is 11%(44313 8K pages of total 393344)
ndb_mgm>