mirror of
https://github.com/prometheus/prometheus.git
synced 2024-12-26 06:04:05 -08:00
scrape: simplify TargetsActive function
Since everything was serialized on a single mutex, it's exactly the same if we process targets in sequence without starting goroutines. Signed-off-by: Bryan Boreham <bjboreham@gmail.com>
This commit is contained in:
parent
aaf5d643b6
commit
f095c33da1
|
@ -279,24 +279,10 @@ func (m *Manager) TargetsActive() map[string][]*Target {
|
|||
m.mtxScrape.Lock()
|
||||
defer m.mtxScrape.Unlock()
|
||||
|
||||
var (
|
||||
wg sync.WaitGroup
|
||||
mtx sync.Mutex
|
||||
)
|
||||
|
||||
targets := make(map[string][]*Target, len(m.scrapePools))
|
||||
wg.Add(len(m.scrapePools))
|
||||
for tset, sp := range m.scrapePools {
|
||||
// Running in parallel limits the blocking time of scrapePool to scrape
|
||||
// interval when there's an update from SD.
|
||||
go func(tset string, sp *scrapePool) {
|
||||
mtx.Lock()
|
||||
targets[tset] = sp.ActiveTargets()
|
||||
mtx.Unlock()
|
||||
wg.Done()
|
||||
}(tset, sp)
|
||||
targets[tset] = sp.ActiveTargets()
|
||||
}
|
||||
wg.Wait()
|
||||
return targets
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in a new issue