Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why the Lock and Unlock method need "m.nodem.Lock"? #19

Open
zjfqxa opened this issue Oct 31, 2017 · 0 comments
Open

why the Lock and Unlock method need "m.nodem.Lock"? #19

zjfqxa opened this issue Oct 31, 2017 · 0 comments

Comments

@zjfqxa
Copy link

zjfqxa commented Oct 31, 2017

Hi hjr265,

as I have known, the redis set operation with "NX" will promise distributed lock,
reply, err := redis.String(conn.Do("SET", m.name, value, "NX", "PX", int(m.expiry/time.Millisecond)))

so it confused me, why the Lock and Unlock method need m.nodem.Lock? and will the m.nodem.Lock lead to deadlock?

func (m *Mutex) Lock() error {
	m.nodem.Lock()
	defer m.nodem.Unlock()
        ...
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant