Project

General

Profile

Bug #44

Router connections should check for conflicting logs

Added by Eric Allman almost 3 years ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Routing Layer
Start date:
08/21/2016
Due date:
% Done:

0%


Description

When a router accepts a connection from another router that it has not previously seen, it should check for name clashes. This is particularly problematic if someone is testing an environment on a private GDP cluster and then attempts to join the public cluster. Right now, if there are log name conflicts, the semantics are undefined.

History

#1 Updated by Rick Pratt about 1 year ago

  • Subject changed from Router connections should check for conflicting logs to Router connections should check for conflicting logs (net3 router)

#2 Updated by Rick Pratt about 1 year ago

  • Subject changed from Router connections should check for conflicting logs (net3 router) to Router connections should check for conflicting logs
  • Category set to GDP Version 0

#3 Updated by Eric Allman 3 months ago

  • Project changed from Click GDP Routers to GDP
  • Category changed from GDP Version 0 to Routing Layer

Also available in: Atom PDF