* feat: synchronize access.log client IPs across nodes for global fail2ban limits * fix(nodes): harden cross-node client-IP merge for cluster fail2ban MergeInboundClientIps inserted new rows with the remote node's primary key, which collides with the independently auto-incremented local id and rolled back the whole sync batch — breaking exactly the node-only clients the feature targets. It also never evicted stale IPs, so the 30-minute cutoff was defeated cluster-wide (the master pushed its unpruned table back to nodes, which re-added IPs they had just pruned) and the blobs grew unbounded. - drop the remote id on create (Id=0) and guard the email-unique race with ON CONFLICT DO NOTHING; also fixes a latent Postgres sequence collision - apply the same 30-minute stale cutoff inside the merge and skip creating node-only rows whose IPs are all stale - throttle the IP fetch/merge/push to ~10s (data only refreshes every 10s) instead of running on every 5s traffic tick, cutting SQLite write churn - log the load error on the push path and tidy the merge response message - add unit tests for the merge (remote-id, dedup, stale-drop, skips) --------- Co-authored-by: Rqzbeh <Rqzbeh@example.com> Co-authored-by: Sanaei <ho3ein.sanaei@gmail.com> |
||
|---|---|---|
| .. | ||
| check_client_ip_job.go | ||
| check_client_ip_job_integration_test.go | ||
| check_client_ip_job_test.go | ||
| check_cpu_usage.go | ||
| check_hash_storage.go | ||
| check_hash_storage_test.go | ||
| check_xray_running_job.go | ||
| clear_logs_job.go | ||
| ldap_sync_job.go | ||
| mtproto_job.go | ||
| node_heartbeat_job.go | ||
| node_traffic_sync_job.go | ||
| node_traffic_sync_job_test.go | ||
| outbound_subscription_job.go | ||
| periodic_traffic_reset_job.go | ||
| stats_notify_job.go | ||
| xray_traffic_job.go | ||