<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - RFE: Support load-balancing targets in systemd-journal-upload"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89185">89185</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>RFE: Support load-balancing targets in systemd-journal-upload
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>duncan@innes.net
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>s-j-upload currently supports a single remote target for streaming logs to.
Ticket <a class="bz_bug_link
bz_status_NEW "
title="NEW - RFE: Support failover targets in systemd-journal-upload"
href="show_bug.cgi?id=89184">https://bugs.freedesktop.org/show_bug.cgi?id=89184</a> is an RFE to expand
this to provide more than 1 target for failover purposes.
This ticket is requesting that the targets can be used in a load-balanced
manner.
At this point, I don't believe the method of load balancing is important. If a
pair (or more) of log receivers are built to cater for failover, it would not
be wise for all logs to go to the receiver #1 under normal circumstances, only
to use receiver #2 in failover circumstances. Clients could be configured to
randomly swap the order of --url targets at configuration time, but this still
allows the heaviest systems to end up with the same receiver #1.
I'm not sure if it would be insensible to round-robin every log entry across
the configured targets, or whether a randomised timer could call for a
switch-over at reasonable points.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>