influxdb 笔记: Retention Police - RPs

本文介绍了InfluxDB中保留策略(RP)的创建及管理方法。RP用于自动删除过期原始数据,并按需聚合历史数据。每个数据库可定义多个RP以适应不同数据管理需求。

https://docs.influxdata.com/influxdb/v0.13/guides/downsampling_and_retention/
# RP 的数据管理策略
https://docs.influxdata.com/influxdb/v0.13/query_language/database_management/#retention-policy-management

#
每个database创建时,默认会自动创建一个RP
每个database可以有多个RP
write时如果不知道RP,默认使用default的RP
当database上有写入时,会自动将数据保存在RP中,RP根据自己的策略进行数据管理


# 语法
CREATE RETENTION POLICY <retention_policy_name> ON <database_name> DURATION <duration> REPLICATION <n> [SHARD DURATION <duration>] [DEFAULT]
DURATION 数据的保留时长. m minutes,h hours,d days,w weeks, INF infinite 不限制.  7230m as 120h 30m
REPLICATION <n>   一个point在cluster中保留几个副本,但在single node instances模式下无效
SHARD DURATION    数据在shard中的保留时长. 默认与 DURATION 相同
u microseconds, ms milliseconds, s seconds,m minutes,h hours,d days,w weeks
不支持复合写法,例如  120h 30m
DEFAULT 作为这个database的默认BP

### 示例
# 目的
automatically delete the raw 10 second level data that are older than two hours
automatically aggregate the 10 second level data to 30 minute level data
keep the 30 minute level data forever

# database: food_data, measurement: orders,  fields: phone and website
# store the number of orders that arrive via each channel every 10 seconds.
CREATE RETENTION POLICY food_two_hours ON food_data DURATION 2h REPLICATION 1 DEFAULT

# 查看
> SHOW RETENTION POLICIES ON food_data
name    duration  replicaN  default
default   0        1        false
two_hours  2h0m0s   1        true

# 指定 RP的查询
SELECT * FROM food_data."default".downsampled_orders LIMIT 5

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/26250550/viewspace-2129324/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/26250550/viewspace-2129324/

# influxd print-config WARN[0000]log.go:228 gosnowflake.(*defaultLogger).Warn DBUS_SESSION_BUS_ADDRESS envvar looks to be not set, this can lead to runaway dbus-daemon processes. To avoid this, set envvar DBUS_SESSION_BUS_ADDRESS=$XDG_RUNTIME_DIR/bus (if it exists) or DBUS_SESSION_BUS_ADDRESS=/dev/null. Command "print-config" is deprecated, use the influx-cli command server-config to display the configuration values from the running server assets-path: "" bolt-path: /root/.influxdbv2/influxd.bolt e2e-testing: false engine-path: /root/.influxdbv2/engine feature-flags: {} flux-log-enabled: false hardening-enabled: false http-bind-address: :8086 http-idle-timeout: 3m0s http-read-header-timeout: 10s http-read-timeout: 0s http-write-timeout: 0s influxql-max-select-buckets: 0 influxql-max-select-point: 0 influxql-max-select-series: 0 instance-id: "" key-name: "" log-level: info metrics-disabled: false nats-max-payload-bytes: 0 nats-port: 0 no-tasks: false overwrite-pid-file: false pid-file: "" pprof-disabled: false query-concurrency: 1024 query-initial-memory-bytes: 0 query-max-memory-bytes: 0 query-memory-bytes: 0 query-queue-size: 1024 reporting-disabled: false secret-store: bolt session-length: 60 session-renew-disabled: false sqlite-path: "" storage-cache-max-memory-size: 1073741824 storage-cache-snapshot-memory-size: 26214400 storage-cache-snapshot-write-cold-duration: 10m0s storage-compact-full-write-cold-duration: 4h0m0s storage-compact-throughput-burst: 50331648 storage-max-concurrent-compactions: 0 storage-max-index-log-file-size: 1048576 storage-no-validate-field-size: false storage-retention-check-interval: 30m0s storage-series-file-max-concurrent-snapshot-compactions: 0 storage-series-id-set-cache-size: 0 storage-shard-precreator-advance-period: 30m0s storage-shard-precreator-check-interval: 10m0s storage-tsm-use-madv-willneed: false storage-validate-keys: false storage-wal-flush-on-shutdown: false storage-wal-fsync-delay: 0s storage-wal-max-concurrent-writes: 0 storage-wal-max-write-delay: 10m0s storage-write-timeout: 10s store: disk strong-passwords: false template-file-urls-disabled: false testing-always-allow-setup: false tls-cert: "" tls-key: "" tls-min-version: "1.2" tls-strict-ciphers: false tracing-type: "" ui-disabled: false vault-addr: "" vault-cacert: "" vault-capath: "" vault-client-cert: "" vault-client-key: "" vault-client-timeout: 0s vault-max-retries: 0 vault-skip-verify: false vault-tls-server-name: "" vault-token: "" 根据配置定位influxdb暂用CPU负载高的原因,并提供解决方案
11-08
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值