"this disconnect reason simply implies that the MQTT client did not notify us that it is disconnecting before we noticed the connection was killed. That means any latency or internet issues would be Amazon's problem.Īfter submitting a ticket, Amazon acknowledged they had experienced degraded network performance during the time of our issues but the internal IoT engineering team added this bit of undocumented info. Those clients were running on EC2 instances. We recently had some MQTT clients lose their connection to the broker with that very disconnect reason. This can happen during a period of high network latency or when the internet connection is lost." "The client-server connection is cut off. Per the AWS Lifecycle Events docs it's description is: This is useful to understand what the root cause of a disconnect is and can initiate some business logic to handle it or report it.ĬONNECTION_LOST is one of the defined reasons. You can see this information in CloudWatch logs and also by subscribing to the special topic When one of your IoT devices disconnects from the IoT Core Broker a log entry is generated with the disconnect reason. These are all things that can influence decisions and it's our job as engineers to solve the problems given the tools at our disposal.Īlmost everything developers argue over with religious zeal are just tools, a means to an end. It just means that there are lots of ways to solve business problems that don't involve the one thing you know a lot about and happen to love.īusiness requirements, timelines, politics, team background. Just remember, in almost all meaningful use cases somebody else could accomplish the same thing with technology Y which you happen to hate.Īnd it definitely doesn't mean there aren't best practices to follow. It also doesn't mean you are wrong to dedicate your career to going deep and mastering technology X. It DOES mean that you should recognize in many instances they are just that, opinions. To be clear, that doesn't mean you shouldn't have strong opinions about your favorite IDE or programming language or database. That is the voice of inexperience talking. "Pattern X is always better than pattern Y" "If you aren't using, you're doing it wrong" "You have to use Visual Studio because Eclipse is the worst" Early in my career I spoke a lot in absolutes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |