Node: Increase channel to bigtable (#2343)
Change-Id: I93410c3dd9d8e2a2afaa76e5e2c66d2ae1a1e2ae
This commit is contained in:
parent
5f224da24c
commit
f2be500799
|
@ -66,7 +66,8 @@ func (re *AttestationEventReporter) Subscribe() *activeSubscription {
|
||||||
re.logger.Debug("Subscribe for client", zap.Int("clientId", clientId))
|
re.logger.Debug("Subscribe for client", zap.Int("clientId", clientId))
|
||||||
channels := &lifecycleEventChannels{
|
channels := &lifecycleEventChannels{
|
||||||
MessagePublicationC: make(chan *MessagePublication, 500),
|
MessagePublicationC: make(chan *MessagePublication, 500),
|
||||||
VAAQuorumC: make(chan *vaa.VAA, 500),
|
// TODO: This channel only needs to be this big due to Pythnet traffic. Once the explorer no longer reads these from bigtable, we can stop writing Pyth messages to this channel.
|
||||||
|
VAAQuorumC: make(chan *vaa.VAA, 1000),
|
||||||
}
|
}
|
||||||
re.subs[clientId] = channels
|
re.subs[clientId] = channels
|
||||||
sub := &activeSubscription{ClientId: clientId, Channels: channels}
|
sub := &activeSubscription{ClientId: clientId, Channels: channels}
|
||||||
|
|
Loading…
Reference in New Issue