You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am new to atlas and trying to configure and play with it. In the Documentation the Netflix Publish API pushes to the Mirrors. How does the publish API know what the mirrors are? I know in the documentation it uses Edda but then how does the publish API know where the Edda API is?
The text was updated successfully, but these errors were encountered:
There are a several ways it can be configured. For the sample config it runs a single node in-memory configuration.
I need to finish merging a couple of the internal parts with oss and document the clustered setup. We currently used edda internally, but it forked and is significantly different than the oss edda right now. I'm trying to refactor some of those parts so it is more pluggable and can actually be used outside of our internal setup. This is taking a bit of time because it isn't strictly beneficial internally so it is a spare time project. I'm about half way done with this refactor though.
brharrington
changed the title
Not an Issue Just a Question
make sharding manager pluggable and document clustered setup
May 31, 2016
I am new to atlas and trying to configure and play with it. In the Documentation the Netflix Publish API pushes to the Mirrors. How does the publish API know what the mirrors are? I know in the documentation it uses Edda but then how does the publish API know where the Edda API is?
The text was updated successfully, but these errors were encountered: