aregm / nff-go

NFF-Go -Network Function Framework for GO (former YANFF)
BSD 3-Clause "New" or "Revised" License
1.38k stars 156 forks source link

Can't start new clone for segment1 instance #715

Closed Vincent7978 closed 4 years ago

Vincent7978 commented 4 years ago
// Initialize NFF-GO library at 16 cores by default
config := flow.Config{
    CPUList:          "0-20",
}
flow.CheckFatal(flow.SystemInit(&config))
inputFlow, err := flow.SetReceiver(uint16(0))
flow.CheckFatal(err)
// Handle second flow via some heavy function
flow.CheckFatal(flow.SetHandler(inputFlow, func(p *packet.Packet, context flow.UserContext) {
    handlePacket(p, context)
}, nil))
flow.CheckFatal(flow.SetStopper(inputFlow))
go saveRecords(inputFlow)
flow.CheckFatal(flow.SystemStart())
WARNING: Can't start new clone for segment1 instance 1
WARNING: Can't start new clone for segment1 instance 3
WARNING: Can't start new clone for segment1 instance 4
WARNING: Can't start new clone for segment1 instance 5
WARNING: Can't start new clone for segment1 instance 6
WARNING: Can't start new clone for segment1 instance 7
WARNING: Can't start new clone for segment1 instance 8
WARNING: Can't start new clone for segment1 instance 9
WARNING: Can't start new clone for segment1 instance 10
WARNING: Can't start new clone for segment1 instance 11
WARNING: Can't start new clone for segment1 instance 12
WARNING: Can't start new clone for segment1 instance 13
WARNING: Can't start new clone for segment1 instance 14
WARNING: Can't start new clone for segment1 instance 15

hi: My code is used like the above, but there will be the following warning in the terminal. What is the problem? Does it have any effect?