pva search period
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- networking
Research direction
Start by reading ChannelSearch.java and PVASettings.java to see how MAX_SEARCH_PERIOD is defined and used, then compare the search behavior with the pvxs netconfig documentation linked in the issue. The requested direction is a configurable, longer search period with exponential backoff; done means the setting can be adjusted for the Archiver Appliance and the search backs off as intended.
Written by the indexing model from the issue text.
Description
Is there a reason why MAX_SEARCH_PERIOD is hard coded in ChannelSearch.java? I'm wondering if it makes sense to be in the PVASettings.java instead.
It looks like from https://epics-base.github.io/pvxs/netconfig.html that pvxs does an exponential backoff, whereas from my initial reading that ChannelSearch does up to 30 seconds increasing in a second at a time.
Since the broadcasts can affect the network when this library is used in the Archiver Appliance I think it makes sense in the archiver to have a much longer MAX_SEARCH_PERIOD, and to have exponential backoff.
fyi @mdavidsaver @kasemir
- Dominant language
- Java
- Stars
- 130
- Forks
- 132
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ControlSystemStudio/phoebus
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ControlSystemStudio/phoebus#3983 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ControlSystemStudio/phoebus#3979 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ControlSystemStudio/phoebus#3962 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ControlSystemStudio/phoebus#3865 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ControlSystemStudio/phoebus#3995 ·
Maintainers usually reply within 1 day
All issues in ControlSystemStudio/phoebus
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 2 days
-
code-health feature/sync OS/Android QA/Test-Plan-Specified QA/Yes
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
brave/brave-browser#60327 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aws/context-ontology-accelerator#325 ·
Maintainers usually reply within 1 day
-
The README tells to run `mvn jeo:disassemble`, which fails with `No plugin found for prefix 'jeo'`Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
objectionary/jeo-maven-plugin#1938 ·
Maintainers usually reply within 2 days
-
effort/l priority/p2 risk/high triage/deferred
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
iflytek/skillhub#1039 · 1 comment ·
Maintainers usually reply within 1 day