Different configurations on servers in Horizontal Scaling Deployment

Hello All,

In a Horizontal scaling deployment with all servers having the same database configuration, is it okay to have the server's Traccar configuration be different on some of them, will it cause any potential problems or issues ?

Example: In some servers the processing.copyAttributes value may contain ignition and in some, it may contain ignition,battery,rpm
or in some, the report.trip.minimalTripDuration value could be different from the rest of the servers.

The reason is that different models of trackers send data to only a set of servers behind a load balancer, and the rest to another load balancer pointed to the remaining servers.

So the configurations are specific to the way the tracker behaves.

Please let me know if you need any additional information or context to better assist me.

It should still work, but some configuration doesn't make sense to be different IMO. For example, if report.trip.minimalTripDuration is different, you might have random results for the report.

Thank you for the answer.

Actually I used the configuration as a quick example.

I see your point about the random results in reports and will be careful about that :)

In the actual deployment, the idea is only to have different configurations related to how the device and Traccar communicate.

I think one valid example would be : [protocol].timeout

That should be fine.