Default localhost port conflict with others in 9090 and 9092


#1

it is hard to avoid this kind of conflicts in Linux. MapD may make well known to use these ports so others not use them later.


#2

@CharlieCL thank you for the feedback. Do you think it would be better to do this in the product, or in our documentation?


#3

In my case I simply change 9090 to 9093 and 9092 to 9095 in mapd config file. Since I installed MapD first, the other program generated install error. I figured out it was the conflict with MapD ports. It is better to select nobody used ports.


#4

Apache Kafka already uses 9092 as its standard port, so it’s somewhat too late. At some point we might switch the defaults, but ultimately, there’s only so many ports! That’s why they are configurable :slight_smile: