Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • PostgreSQL

    Have information about logical read and physical and logical  read /write page pages for indexes and table tables separately and for whole database. With the same granularity has time spent for physical operations. Also statistics available on SQL statements level.

...

  1. Implement gathering local node statistics with two levels of detalization: fine-grain by type of page types (about 35 such types) and aggregated statistics: INDEX, DATA, OTHER. Need to support 3 types of IO operations: logical/physical read , and physical read/writewrite (only as global statistics).
  2. Implement collecting local node statistics with the following dimensions: cache, index, query.
  3. implement exchange IO statistics by nodes to have ability expose cluster statistics (e.g. IO statistics for distributed SQL). 
  4. expose IO statistics interfaces for SQL, JMX, Visor, CMD, Web Console

...

  • Cluster wide statistics, can lead performance issue
  • which of interfaces should be exposed: SQL, JMX, Visor, CMD, Web Console ....
  • reset of statistics. It can be by request, by time, some metrics value, .... or may be reset by time and keep history of metrics.
  • .....

Tickets

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = Ignite AND labels IN (iep-27) ORDER BY status
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
// Links or report with relevant JIRA tickets.