commit | 3baf916062f65341088051f95d1ec37924163052 | [log] [tgz] |
---|---|---|
author | tornado-ssy <64736788+tornado-ssy@users.noreply.github.com> | Mon Aug 28 22:49:22 2023 +0800 |
committer | GitHub <noreply@github.com> | Mon Aug 28 22:49:22 2023 +0800 |
tree | 121e082c5ac0defb92dd795f96355e9c6fc44add | |
parent | 0e43daf2d15cc736b598c6a7c1ec69d58ddef83d [diff] |
修复wait长查询场景下配置项发生变化,更新缓存失败 (#294) * 修复kie日志打印配置信息 * 修复健康检查被限流住 * 修复watch场景下配置项长时间不改变且持续调用而发生的内存溢出问题 * 修复watch场景下配置项长时间不改变且持续调用而发生的内存溢出问题 * 修复wait长查询时配置发生变化场景下,更新缓存失效 * 修复wait长查询时配置发生变化场景下,更新缓存失效 * 修复wait长查询时配置发生变化场景下,更新缓存失效 * 修复wait长查询时配置发生变化场景下,更新缓存失效 * 修复wait长查询时配置发生变化场景下,更新缓存失效 --------- Co-authored-by: songshiyuan 00649746 <songshiyuan3@huawei.com>
A service for configuration management in distributed system.
Key could indicate a configuration like “timeout”, then the value could be “3s” or indicates a file name “app.properties”, then the value could be content of app.properties
Each key could has labels. labels indicates a unique key. A key “log_level” with labels “env=production” may saves the value “INFO” for all application log level in production environment. A key “log_level” with labels “env=production, component=payment” may saves the value “DEBUG” for payment service in production environment.
It means all payment service print debug log, but for other service print info log.
So you can control your application runtime behaviors by setting different labels to a key.
kie is a highly flexible config server. Nowadays, an operation team is facing different “x-centralized” system. For example a classic application-centralized system. A operator wants to change config based on application name and version, then the label could be “app,version” for locating a app‘s configurations. Meanwhile some teams manage app in a data center, each application instance will be deployed in a VM machine. then label could be “farm,role,server,component” to locate a app’s configurations. kie fit different senario for configuration management which benifit from label design.
It includes 1 components
git clone git@github.com:apache/servicecomb-kie.git cd servicecomb-kie/deployments/docker sudo docker-compose up
It will launch 3 components
To see how to build a local dev environment, check here
This will build your own service image and binary in local
cd build export VERSION=0.0.1 #optional, it is latest by default ./build_docker.sh
This will generate a “servicecomb-kie-0.0.1-linux-amd64.tar” in “release” folder, and a docker image “servicecomb/kie:0.0.1”
After you launch kie server, you can browse API doc in http://127.0.0.1:30110/apidocs.json, copy this doc to http://editor.swagger.io/
https://kie.readthedocs.io/en/latest/
or follow here to generate it in local
Bugs: issues
See Contribution guide for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issues.