> You could additionally try to tweak
> caf#middleman.max_consecutive_reads, which configures how many
> new_data_msg messages a broker receives from the backend in a single
> shot. It makes sense to have the two separated, because one configures
> fairness in the scheduling and the other fairness
[
https://bro-tracker.atlassian.net/browse/BIT-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=24707#comment-24707
]
Aaron Eppert commented on BIT-1541:
---
I do have a, rather large, core file associated with this event, again.
[
https://bro-tracker.atlassian.net/browse/BIT-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Sommer updated BIT-1546:
--
Resolution: Merged (was: Fixed)
Status: Closed (was: Merge Request)
> Please merge
[
https://bro-tracker.atlassian.net/browse/BIT-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Sommer reassigned BIT-1543:
-
Assignee: Robin Sommer (was: Seth Hall)
> Kafka Logger - Writes Bro Logs to Kafka
>
[
https://bro-tracker.atlassian.net/browse/BIT-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Sommer reassigned BIT-1546:
-
Assignee: Robin Sommer
> Please merge topic/johanna/str-functions
>
[
https://bro-tracker.atlassian.net/browse/BIT-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Sommer reassigned BIT-1547:
-
Assignee: Justin Azoff
> broctl sets the same state variables over and over
>
> the benchmark no longer
> terminates and the server quickly stops getting data, and I would like
> to know why.
I'll have a look at it.
> I've tried various parameters for the scheduler throughput, but they do
> not seem to make a difference. Would you mind taking a look at what's
> going on
Open Merge Requests
===
IDComponentReporterAssigneeUpdated For Version
PrioritySummary
--- -- -- --
- --
--
