尽量服用,和优化采样区块,交易所在区块的资源参数 获取不需要每次获取有下单租赁订单都获取一遍,应该是全局异步获取是不是就可以,帮我设计合理方案。 和清理逻辑
This commit is contained in:
1 parent
13665668ac
commit
1538cd0819
24 files changed
+1894
-230
No files matched your search
@@ -8,6 +8,9 @@ rental:
|
||||
# 正常在线、无排队且RPC及时返回时,调度+推送等待约0~5秒,目标10秒左右接单。
|
||||
# 均为上轮执行完成后的等待时间;链上查询耗时不包含在间隔中。修改后重启服务端。
|
||||
delivery:
|
||||
# 提交后立即异步派单/推送;以下周期只做持久化补偿扫描。
|
||||
workers: ${RENT_DELIVERY_WORKERS:4}
|
||||
queue-capacity: ${RENT_DELIVERY_QUEUE_CAPACITY:200}
|
||||
dispatch-interval-ms: ${RENT_DELIVERY_DISPATCH_INTERVAL_MS:3000}
|
||||
push-interval-ms: ${RENT_DELIVERY_PUSH_INTERVAL_MS:2000}
|
||||
payment:
|
||||
@@ -47,6 +50,20 @@ rental:
|
||||
networks: ${RENT_HISTORY_NETWORKS:NILE}
|
||||
poll-interval-ms: ${RENT_HISTORY_POLL_MS:1000}
|
||||
batch-size: ${RENT_HISTORY_BATCH_SIZE:30}
|
||||
# 短暂参数归档落后先重试;超过等待期仍缺证据才进入原人工核对流程。
|
||||
parameter-grace-seconds: ${RENT_HISTORY_PARAMETER_GRACE_SECONDS:120}
|
||||
# 参数采样停滞则暂停新资源派单,保留订单等待和原有资金保护。
|
||||
max-sample-age-seconds: ${RENT_HISTORY_MAX_SAMPLE_AGE_SECONDS:15}
|
||||
cleanup:
|
||||
# 已有历史库先执行sql/rent_history_cleanup_upgrade.sql;仅归档清理历史表。
|
||||
enabled: ${RENT_HISTORY_CLEANUP_ENABLED:true}
|
||||
# 使用UTC,每天03:15执行;保留期外仍会保护未闭环订单和最近10000个区块。
|
||||
cron: ${RENT_HISTORY_CLEANUP_CRON:0 15 3 * * ?}
|
||||
retention-days: ${RENT_HISTORY_RETENTION_DAYS:30}
|
||||
batch-size: ${RENT_HISTORY_CLEANUP_BATCH_SIZE:500}
|
||||
max-batches: ${RENT_HISTORY_CLEANUP_MAX_BATCHES:200}
|
||||
# 必须是可写、支持原子移动的持久目录;归档文件不会自动删除。
|
||||
archive-directory: ${RENT_HISTORY_ARCHIVE_DIRECTORY:./data/rental-history-archive}
|
||||
probe-address: ${RENT_HISTORY_PROBE_ADDRESS:T9yD14Nj9j7xAB4dbGeiX9h8unkKHxuWwb}
|
||||
# 外部历史服务兼容配置;开启embedded-enabled后走Java内部调用,不需要填写这两项。
|
||||
nile: ${RENT_NILE_HISTORY:}
|
||||
|
||||
Reference in new issue
Block a user