Got it. I found that I forgot to add `time.Sleep` in `main()` function so there would be some schedule problem, now I fix the problem. Thanks.
On Sat, Nov 20, 2021 at 10:31 AM Kurtis Rader <kra...@skepticism.us> wrote: > On Fri, Nov 19, 2021 at 8:30 AM ChrisFisher <yangfishe...@gmail.com> > wrote: > >> Hey Guys, I want to do a micro benchmark, and I have one master machine >> and one worker machine. The master machine sends out rpcs concurrently to >> the worker, and after the worker receive the rpc, it starts to do some >> commands using exec.Command. Here are parts of my code. master code >> <https://play.golang.org/p/lN3WxPfkqyw> and, worker code >> <https://play.golang.org/p/WxhPoztrWOn>. I use a channel of size 12 to >> simulate there are only 12 threads in worker machine. But the whole >> procedure stuck at the point of >> cmd.Run() and I don't know why because the command is just simply echo a >> hello. I did some experiments on rpc and exec.Command, they worked out >> perfectly without each other. But when I combined them, it stuck. I don't >> know, does anyone know what happen? >> > > Insufficient data since your playground worker example does not include > the rpc components or a `main()` function. I would start by killing the > worker process with SIGABRT. That should produce Go stack traces which are > likely to provide useful clues. > > -- > Kurtis Rader > Caretaker of the exceptional canines Junior and Hank > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAL2p2H-XvB12WHdexud9AZNfsDJThb4ASkJceBPKCFRi6H0%2BBw%40mail.gmail.com.
