d435f1211e
When multiple clients try to connect concurrently using the same client ID, they all call `emqx_channel:ensure_connected`, increasing the live connection count, but only one will successfully acquire the lock for that client ID. This means that all other clients that increased the live connection count will not get to call neither `emqx_channel:ensure_disconnected` nor be monitored for `DOWN` messages, effectively causing a count leak. By moving the increment to `emqx_cm:register_channel`, which is only called inside the lock, we can remove this leakage. Also, during the handling of `DOWN` messages, we now iterate over all channel PIDs returned by `eqmx_misc:drain_down`, since it could be that one or more PIDs are not contained in the `pmon` state. |
||
|---|---|---|
| .ci | ||
| .github | ||
| apps | ||
| bin | ||
| data | ||
| deploy | ||
| etc | ||
| include | ||
| lib-ce | ||
| lib-extra | ||
| priv | ||
| scripts | ||
| src | ||
| test | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .tool-versions | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README-CN.md | ||
| README-JP.md | ||
| README-RU.md | ||
| README.md | ||
| Windows.md | ||
| build | ||
| elvis.config | ||
| pkg-vsn.sh | ||
| rebar.config | ||
| rebar.config.erl | ||
README.md
EMQ X Broker
English | 简体中文 | 日本語 | русский
EMQ X broker is a fully open source, highly scalable, highly available distributed MQTT messaging broker for IoT, M2M and Mobile applications that can handle tens of millions of concurrent clients.
Starting from 3.0 release, EMQ X broker fully supports MQTT V5.0 protocol specifications and backward compatible with MQTT V3.1 and V3.1.1, as well as other communication protocols such as MQTT-SN, CoAP, LwM2M, WebSocket and STOMP. The 3.0 release of the EMQ X broker can scaled to 10+ million concurrent MQTT connections on one cluster.
- For full list of new features, please read EMQ X Release Notes.
- For more information, please visit EMQ X homepage.
Installation
The EMQ X broker is cross-platform, which supports Linux, Unix, macOS and Windows. It means EMQ X can be deployed on x86_64 architecture servers and ARM devices like Raspberry Pi.
See more details for building and running EMQ X on Windows in Windows.md
Installing via EMQ X Docker Image
docker run -d --name emqx -p 1883:1883 -p 8081:8081 -p 8083:8083 -p 8883:8883 -p 8084:8084 -p 18083:18083 emqx/emqx
Installing via Binary Package
Get the binary package of the corresponding OS from EMQ X Download page.
Build From Source
The EMQ X broker requires Erlang/OTP R21+ to build since 3.0 release.
For 4.3 and later versions.
git clone https://github.com/emqx/emqx.git
cd emqx
make
_build/emqx/rel/emqx/bin console
For earlier versions, release has to be built from another repo.
git clone https://github.com/emqx/emqx-rel.git
cd emqx-rel
make
_build/emqx/rel/emqx/bin/emqx console
Quick Start
If emqx is built from source, cd _build/emqx/rel/emqx.
Or change to the installation root directory if emqx is installed from a release package.
# Start emqx
./bin/emqx start
# Check Status
./bin/emqx_ctl status
# Stop emqx
./bin/emqx stop
To view the dashboard after running, use your browser to open: http://localhost:18083
Test
To test everything in one go
make eunit ct
To run subset of the common tests
Examples
make apps/emqx_bridge_mqtt-ct
Dialyzer
To Analyze all the apps
make dialyzer
To Analyse specific apps, (list of comma separated apps)
DIALYZER_ANALYSE_APP=emqx_lwm2m,emqx_auth_jwt,emqx_auth_ldap make dialyzer
Community
FAQ
Visiting EMQ X FAQ to get help of common problems.
Questions
GitHub Discussions is where you can ask questions, and share ideas.
Proposals
For more organised improvement proposals, you can send pull requests to EIP.
Plugin development
To develop your own plugins, see lib-extra/README.md
MQTT Specifications
You can read the mqtt protocol via the following links:
License
Apache License 2.0, see LICENSE.