终止第二个 goroutine。

huangapple go评论82阅读模式
英文:

Terminate the second goroutine

问题

我有以下的代码片段。

package main

import (
	"errors"
	"fmt"
	"time"
)

func errName(ch chan error) {

	for i := 0; i < 10000; i++ {

	}

	ch <- errors.New("Error name")
	close(ch)
}

func errEmail(ch chan error) {

	for i := 0; i < 100; i++ {

	}
	ch <- errors.New("Error email")
	close(ch)
}

func main() {

	ch := make(chan error)

	go errName(ch)
	go errEmail(ch)
	fmt.Println(<-ch)
	//close(ch)

	time.Sleep(1000000)

}

如你所见,我让两个函数在 goroutine 中运行,errName 和 errEmail。我将一个 error 类型的 channel 作为参数传递进去。如果其中一个函数先完成,它应该通过 channel 发送错误并关闭它。因此,仍在运行的第二个 goroutine 就不需要再运行了,因为我已经得到了错误并且想要终止仍在运行的 goroutine。这就是我在上面的示例中试图实现的目标。

当我运行程序时,我得到了错误:

panic: send on closed channel

goroutine 6 [running]:
main.errEmail(0xc0820101e0)
        D:/gocode/src/samples/gorountine2.go:24 +0xfd
created by main.main
        D:/gocode/src/samples/gorountine2.go:33 +0x74

goroutine 1 [runnable]:
main.main()
        D:/gocode/src/samples/gorountine2.go:34 +0xac
exit status 2

我知道,如果我移除 close 语句,它就不会发生 panic,但是仍在运行的 goroutine 上的 channel 仍在等待错误引用,这意味着它浪费了内存(等待中)。

当其中一个函数向 channel 发送错误时,我就不再关心第二个错误了,这是我的目标。

英文:

I have the following code snippet.

package main

import (
	&quot;errors&quot;
	&quot;fmt&quot;
	&quot;time&quot;
)

func errName(ch chan error) {

	for i := 0; i &lt; 10000; i++ {

	}

	ch &lt;- errors.New(&quot;Error name&quot;)
	close(ch)
}

func errEmail(ch chan error) {

	for i := 0; i &lt; 100; i++ {

	}
	ch &lt;- errors.New(&quot;Error email&quot;)
	close(ch)
}

func main() {

	ch := make(chan error)

	go errName(ch)
	go errEmail(ch)
	fmt.Println(&lt;-ch)
	//close(ch)

	time.Sleep(1000000)

}

As you can see, I let two functions run in the goroutine, errName and errEmail. I pass as parameter a channel with error type. If one of them finish first, it should send the error through the channel and close it. So the second, still running goroutine, have not to run anymore, because I've got the error already and I want to terminate the still running goroutine. This is what I trying to reach in my example above.

When I run the programm, I've got error

panic: send on closed channel

goroutine 6 [running]:
main.errEmail(0xc0820101e0)
        D:/gocode/src/samples/gorountine2.go:24 +0xfd
created by main.main
        D:/gocode/src/samples/gorountine2.go:33 +0x74

goroutine 1 [runnable]:
main.main()
        D:/gocode/src/samples/gorountine2.go:34 +0xac
exit status 2

I know, when I remove the close statement, it would not panic, but channel on the running goroutine is still waiting for error reference and that's mean, it wasted the memory for nothing(waiting).

When one of them send an error to the channel, the second error I will do not care anymore, that is my target.

答案1

得分: 3

一种常见的组织这些行为的方法是使用以下代码:

package main

import (
	"fmt"
	"time"

	"code.google.com/p/go.net/context"
)

func errName(ctx context.Context, cancel context.CancelFunc) {
	for i := 0; i < 10000; i++ {
		select {
		case <-ctx.Done():
			return
		default:
		}
	}
	cancel()
}

func errEmail(ctx context.Context, cancel context.CancelFunc) {

	for i := 0; i < 100; i++ {
		select {
		case <-ctx.Done():
			return
		default:
		}
	}
	cancel()
}

func main() {

	ctx := context.Background()

	ctx, cancel := context.WithCancel(ctx)

	go errName(ctx, cancel)
	go errEmail(ctx, cancel)

	<-ctx.Done()

	if ctx.Err() != nil {
		fmt.Println(ctx.Err())
	}

	time.Sleep(1000000)

}

你可以阅读两篇关于这个问题的好文章:

  1. http://blog.golang.org/context
  2. http://blog.golang.org/pipelines
英文:

A standard way to organize this behaviors is to use

package main

import (
	&quot;fmt&quot;
	&quot;time&quot;

	&quot;code.google.com/p/go.net/context&quot;
)

func errName(ctx context.Context, cancel context.CancelFunc) {
	for i := 0; i &lt; 10000; i++ {
		select {
		case &lt;-ctx.Done():
			return
		default:
		}
	}
	cancel()
}

func errEmail(ctx context.Context, cancel context.CancelFunc) {

	for i := 0; i &lt; 100; i++ {
		select {
		case &lt;-ctx.Done():
			return
		default:
		}
	}
	cancel()
}

func main() {

	ctx := context.Background()

	ctx, cancel := context.WithCancel(ctx)

	go errName(ctx, cancel)
	go errEmail(ctx, cancel)

	&lt;-ctx.Done()

	if ctx.Err() != nil {
		fmt.Println(ctx.Err())
	}

	time.Sleep(1000000)

}

You can read two good articles on the matter:

  1. http://blog.golang.org/context
  2. http://blog.golang.org/pipelines

答案2

得分: 2

使用另一个通道来信号完成:

package main

import (
    "errors"
    "fmt"
    "time"
)

func errName(ch chan error, done chan struct{}) {
    for i := 0; i < 10000; i++ {
        select {
        case <-done:
            fmt.Println("从 name 函数提前返回")
            return
        default:
        }
    }
    select {
    case ch <- errors.New("错误名称"):
    default:
    }
}

func errEmail(ch chan error, done chan struct{}) {
    for i := 0; i < 100; i++ {
        select {
        case <-done:
            fmt.Println("从 email 函数提前返回")
            return
        default:
        }
    }
    select {
    case ch <- errors.New("错误邮箱"):
    default:
    }
}

func main() {
    ch := make(chan error, 1)
    done := make(chan struct{})
    go errName(ch, done)
    go errEmail(ch, done)
    fmt.Println(<-ch)
    close(done)
    time.Sleep(1000000)
}

为了防止丢失的 goroutine 在通道发送时永远阻塞,我使用容量为 1 的错误通道,并在发送时使用了 select:

select {
case ch <- errors.New("错误邮箱"):
default:
}

如果你正在处理多个级别的 goroutine 完成,那么你应该考虑使用 golang/x/net/context Context

英文:

Use another channel to signal done:

package main

import (
    &quot;errors&quot;
    &quot;fmt&quot;
    &quot;time&quot;
)

func errName(ch chan error, done chan struct{}) {
    for i := 0; i &lt; 10000; i++ {
        select {
        case &lt;-done:
            fmt.Println(&quot;early return from name&quot;)
            return
        default:
        }
    }
    select {
    case: ch &lt;- errors.New(&quot;Error name&quot;)
    default:
    }
}

func errEmail(ch chan error, done chan struct{}) {
    for i := 0; i &lt; 100; i++ {
        select {
        case &lt;-done:
            fmt.Println(&quot;early return from email&quot;)
            return
        default:
        }
    }
    select {
    case ch &lt;- errors.New(&quot;Error email&quot;):
    default:
    }
}

func main() {
    ch := make(chan error, 1)
    done := make(chan struct{})
    go errName(ch, done)
    go errEmail(ch, done)
    fmt.Println(&lt;-ch)
    close(done)
    time.Sleep(1000000)
}

playground example

To prevent the losing goroutine from blocking forever on channel send, I created the error channel with capacity 1 and use a select when sending:

select {
case ch &lt;- errors.New(&quot;Error email&quot;):
default:
}

If you are working with more than one level of goroutine completion, then you should consider using golang/x/net/context Context.

答案3

得分: 1

Done chan struct{}提到(或其context.Context版本)是行为的惯用和真正的方式。但是在你的代码片段中避免panic的简单方法可以是:

import "sync"

var once sync.Once

func errName(ch chan error) {
    for i := 0; i < 10000; i++ {
    
    }
    once.Do(func() {ch <- errors.New("Error name"); close(ch)}())
}
func errName(ch chan error) {
    for i := 0; i < 10000; i++ {

    }
    once.Do(func() {ch <- errors.New("Error name"); close(ch)}())
}

请注意,我只翻译了代码部分,其他内容不包括在内。

英文:

Done chan struct{} mentioned (or its context.Context incarnation) is the idiomatic and THE TRUE way for behaviour. But the easy way to avoid panic in your snippet can be

import &quot;sync&quot;

var once sync.Once

func errName(ch chan error) {
    for i := 0; i &lt; 10000; i++ {
    
    }
  	once.Do(func() {ch &lt;- errors.New(&quot;Error name&quot;); close(ch)}())
}
func errName(ch chan error) {
    for i := 0; i &lt; 10000; i++ {

    }
    once.Do(func() {ch &lt;- errors.New(&quot;Error name&quot;); close(ch)}())
 }

huangapple
  • 本文由 发表于 2015年1月15日 00:05:49
  • 转载请务必保留本文链接:https://go.coder-hub.com/27947325.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定