on the same network, make sure you're using unique names. # cluster.name: elasticsearch cluster.routing.schedule: 50ms #################################### Node ##################################### During the initial recovery # #cluster.routing.allocation.node_initial_primaries_recoveries: 4 # # 2. During adding/removing nodes, rebalancing, etc # #cluster.routing.allocation.node_concurrent_recoveries: • http.enabled • node.data • node.name • node.master • path.data • network.host • cluster.routing.schedule • path.plugins • http.cors.enabled • http.cors.allow-origin The advantage of using this

kind of appender that you use "inside" another appender. It allows you to create some kind of "routing" between a chain of appenders. The most used "nested compliant" appender are: • The AsyncAppender