Fair enough for sending the file. But what about the reply? That can also be pretty big, is there a preferred pattern or helpers to get that across without hitting the maximum payload?
With regards, Jos Houtman On Tuesday, July 4, 2017 at 6:11:02 PM UTC+2, R.I.Pienaar wrote: > > > > On Tue, Jul 4, 2017, at 17:57, jhoutman via mcollective-users wrote: > > Hi group, > > > > > > We have build a few custom mcollective plugins, that are build on the > > rpcclient. > > > > With one of those we now get the following error: > > natswrapper.rb:138:in `block in start' Disconnected from NATS: > > NATS::IO::ServerError: 'Maximum Payload Violation' > > > > The code uses Mcollective::RPC#rpcclient. One of the arguments send > over > > the line is the content of a user provided file. > > And in this scenario the whole message is bigger then the 1MB payload > > limit. > > > > > > Is it possible that the mcollective rpcclient starts chunking these > > requests? > > Or should we look towards solving the issue of that transfer in another > > way. > > for sure using middleware to transfer files is not really a great idea, > I'd > use mco to initiate a rsync or something instead > -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mcollective-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
