Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is this the correct way to terminate a goroutine in golang?

Tags:

go

I am building a command line app which needs to start its own HTTP server. My idea is to start the http server inside a goroutine in my main program like this:

func main() {
    go myserver()

    // perform lots of time-consuming tasks
}

func myserver() {
    s := &http.Server{
        Addr: ":8080",
        Handler: MyHandler{},
    }
    log.Fatal(s.ListenAndServe())
}
  1. My main function needs to be able to tell the goroutine to die. Since the webserver is blocking on the ListenAndServe method, there is no way of signalling via a sync.WaitGroup or a channel.
  2. One idea I have is to make a HTTP POST to the webserver and ask it to commit suicide on receiving a specific agreed-upon value.

Are there other alternatives that are idiomatic to golang ?

like image 697
canadadry Avatar asked Mar 03 '14 04:03

canadadry


People also ask

What happens to Goroutine when main exits?

When the main goroutine returns, the entire runtime system quits, rather abruptly. Hence any goroutines that are stuck waiting to send on an unbuffered or full channel simply ... cease to exist.

Can you return from a Goroutine?

The answer is yes. If the function that calls a goroutine exits(returns) before the thread(goroutine) finishes.

Is a Goroutine a thread?

A goroutine is a lightweight thread managed by the Go runtime.

What is a Goroutine in Golang?

Golang provides goroutines to support concurrency in Go. A goroutine is a function that executes simultaneously with other goroutines in a program and are lightweight threads managed by Go. A goroutine takes about 2kB of stack space to initialize.


1 Answers

If you are running the web interface until the program exits, you can just return from the main thread. Returning from the main thread exits the program even if another goroutine is working. If you want the main thread to send a kill to the http server, the best way is to close the listener.

func main() {
    l, err := net.Listen("tcp", ":8080")
    if err != nil {
        log.Fatal(err)
    }
    go myserver(l)

    // perform lots of time-consuming tasks

    l.Close()
}

func myserver(l net.Listener) {
    s := &http.Server{
        Addr:    ":8080",
        Handler: MyHandler{},
    }
    log.Print(s.Serve(l))
}

This will not close connections already open. It will only prevent new ones from being created. You need to add logic to your handler and/or stop keep-alives to ensure that the connection isn't reused for long after you kill listener.

like image 114
Stephen Weinberg Avatar answered Oct 17 '22 10:10

Stephen Weinberg