KnowStreaming icon indicating copy to clipboard operation
KnowStreaming copied to clipboard

一站式云原生实时流数据平台,通过0侵入、插件化构建企业级Kafka服务,极大降低操作、存储和管理实时流数据门槛

Results 197 KnowStreaming issues
Sort by recently updated
recently updated
newest added

### 环境信息 k8s集群版本为1.23.1,ipv4/ipv6双栈集群,网络插件为calico Helm部署包:knowstreaming-manager-0.1.9.tgz ### 问题 1. knowstreaming-manager和knowstreaming-web不断重启 2. ksmysql没有调整cpu和内存资源的时候,状态为OOM,直到调整为8C32G才启动成功 ### **重现该问题的步骤** 1. 在k8s集群中进行部署 ```bash helm install kafka-ui ../knowstreaming-manager -f values.yaml -n kafka-ui ``` 2. 输出结果 ```bash NAME READY STATUS...

status: pending

http://npm.taobao.org和 http://registry.npm.taobao.org 将在 2022.06.30 号正式下线和停止 [DNS](https://so.csdn.net/so/search?q=DNS&spm=1001.2101.3001.7020) 解析。新域名为 npmmirror.com, 相关服务域名切换规则请参考: http://npm.taobao.org => http://npmmirror.com http://registry.npm.taobao.org => http://registry.npmmirror.com

- [ ] 我已经在 [issues](https://github.com/didi/KnowStreaming/issues) 搜索过相关问题了,并没有重复的。 ### 环境信息 * KnowStreaming version : 3.4.0 * Operating System version : CentOS Linux release 7.9.2009 * Java version : java version "11.0.2" 2019-01-15...

type: bug
dev: front-end

## 变更的目的是什么 consumer列表支持按status和member数量排序后端实现接口 ## 简短的更新日志 consumer列表支持按status和member数量排序后端实现接口 ## 验证这一变化 consumer列表支持按status和member数量排序后端实现接口

问题:目前公有云的kafka基本上不对外暴露zk端口,导致在实例录入的时候就失败了。是否可以只录入bootstrap-server

- [x] 我已经在 [issues](https://github.com/didi/KnowStreaming/issues) 搜索过相关问题了,并没有重复的。 ## deployment部署的knowstreaming,接入statefulset部署的kafka集群提示超时 ``` [root@k8s-master-01:~] # kubectl get pod -n knowstreaming NAME READY STATUS RESTARTS AGE elasticsearch-957f899bd-p9fcc 1/1 Running 0 24h knowstreaming-manager-6747759bc8-6rfg2 1/1 Running 0 23h...

The know streaming has not any update since last year, and kafka had released two main versions and maybe upgraded to 4.0 at the end of 2024, what's our plan...

- [ ] 我已经在 [issues](https://github.com/didi/KnowStreaming/issues) 搜索过相关问题了,并没有重复的。 ## 在这里提出你的问题 2024-07-09 15:22:00.170 ERROR 3183380 --- [ool-7-thread-18] errorLogger : method=doQuery||indexName=[ks_kafka_topic_metric_2024-07-08,ks_kafka_topic_metric_2024-07-09]||queryDsl={"query":{"bool":{"must":[{"term":{"clusterPhyId":{"value":1}}},{"term":{"topic":{"value":"order_bike"}}},{"term":{"brokerAgg":{"value":"1"}}},{"range":{"timestamp":{"gte":1720509120167,"lte":1720509720167}}}],"must_not":[{"term":{"metrics.PartitionURP":{"value":0.0}}}]}}}||errMsg=query error. org.elasticsearch.common.util.concurrent.UncategorizedExecutionException: Failed execution at org.elasticsearch.action.support.AdapterActionFuture.rethrowExecutionException(AdapterActionFuture.java:91) at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:74) at com.xiaojukeji.know.streaming.km.persistence.es.ESOpClient.doQuery(ESOpClient.java:445) at com.xiaojukeji.know.streaming.km.persistence.es.ESOpClient.performRequestWithRouting(ESOpClient.java:234) at...

- [ ] 我已经在 [issues](https://github.com/didi/KnowStreaming/issues) 搜索过相关问题了,并没有重复的。 ## 在这里提出你的问题 你好,kafaka节点新增,增加的节点Broker-Roles列为空,请问这个Roles是什么意思,为空影响集群吗,如果影响我该如何处理 ![fe64e84a3ce0c8fa4c60bb49cbec05c](https://github.com/didi/KnowStreaming/assets/34936970/d9936e07-319f-4e71-aef4-38e329986933)