Last modified: 2014-06-12 13:36:54 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T68526, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66526 - Consumer that produces to kafka not getting current set of brokers
Consumer that produces to kafka not getting current set of brokers
Status: NEW
Product: Analytics
Classification: Unclassified
EventLogging (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-12 13:36 UTC by christian
Modified: 2014-06-12 13:36 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description christian 2014-06-12 13:36:54 UTC
It seems [1] on 2014-06-12 the eventlogging's consumer that produces to kafka
tried to connect to kafka using
 
  analytics1021.eqiad.wmnet
  analytics1022.eqiad.wmnet

as set of brokers, although the set of brokers at that time was [2]

  analytics1012.eqiad.wmnet
  analytics1021.eqiad.wmnet
  analytics1022.eqiad.wmnet

.

We should make sure that eventloggings consumer that produces to kafka uses
the correct set of brokers.





[1] On 2014-06-12 in #wikimedia-analytics,

  [11:32:39] <nuria>	 Driving tcp://127.0.0.1:8600?socket_id=kafka -> kafka://eqiad?brokers=analytics1021.eqiad.wmnet,analytics1022.eqiad.wmnet&topic=eventlogging-00..

[2] https://git.wikimedia.org/blob/operations%2Fpuppet/ca93720e7125c9dd57093d1a022b001612ec2da0/manifests%2Frole%2Fanalytics%2Fkafka.pp#L54

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links