Databrowser buffer: No history refresh with Epics Archiver Appliance
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by checking how the databrowser uses org.csstudio.trends.databrowser3/automatic_history_refresh and how it transitions from the live buffer to historical data from EPICS Archiver Appliance. Reproduce the reported behavior with the settings described in the issue and compare the red plot with a newly added green plot. Done means the existing plot continues retrieving archived data instead of flatlining when older data leaves the live buffer.
由索引模型根据 Issue 内容生成。
描述
Hello,
I'm researching an issue with our databrowser in combination with Epics Archiver Appliance, but until now, to no avail. Please take a look at the following screenshot. It displays twice the same plot. The red plot is running for a while, the green plot has been added a couple of moments before the screenshot has been made.
As you can see, the red plot fails to retrieve data from the Archiver beyond the live buffer. At a certain point in time, the plot flatlines. As new data comes in, old data falls out. The starting point of the flatline never shifts, except when increasing or decreasing the buffer. When changing the buffer, as expected, the observable amount of live data increases or decreases aswell. The green plot, on the other hand, demonstrates that the data has been correctly archived and can, in principle, be accessed by the databrowser.
I was very glad to discover
org.csstudio.trends.databrowser3/automatic_history_refresh = true
convinced that this will solve the issue, but in fact, it did not change the behavior.
These are the settings I use:
There is no firewall involved, neither on the archivers side nor on the side of Phoebus.
A look at this last screenshot confirms that the point in time where both plots start flatlining is in sync, further confirming that the issue seems to be with the transition from live buffer to historical data.
I'd love to here your ideas what could be a reason for this issue and what a possible solution might look like!
Kind regards!
- 主要语言
- Java
- 星标
- 130
- 派生
- 132
- 平均合并
- 2 天 11 小时
- 30 天内合并 PR
- 19
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ControlSystemStudio/phoebus 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
ControlSystemStudio/phoebus#3983 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
ControlSystemStudio/phoebus#3979 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 80/100
ControlSystemStudio/phoebus#3962 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
ControlSystemStudio/phoebus#3865 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 52/100
ControlSystemStudio/phoebus#3980 ·
维护者通常 2 天内回复
查看 ControlSystemStudio/phoebus 的全部 Issue
相似的 Issue
-
dev/release: verify-release-candidate.sh runs 0 Java tests with Debian's Maven可能已有人在做 @kou 今天认领。 未关闭Type: bug
难度 2/5 1-3 小时 新手友好度 72/100
apache/arrow-adbc#4947 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
checkstyle/checkstyle#22153 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
Documentation Needs Triage
难度 1/5 1 小时以内 新手友好度 78/100
frankframework/frankframework#11908 ·
维护者通常 1 天内回复