master slave setup - Mesh networks

Question

Let's say I have a big physical open-space with hundreds of IoT devices interconnected to each other through a mesh network (adhoc wifi) and each device obviously has its own data. Since it's a really big open space, the wifi router or access point can only reach some 10% of all those 100 nodes, i.e. 10 nodes. So, these are primary master nodes and rest are slaves. Also, slaves could have their own slaves and be called as Secondary Masters. So the hierarchy is almost like that of a typical organization, where everyone will have a master and only 10% of them will have access to the internet.
And, the goal is to collect data from all the nodes and push it to the central database that could be hosted on AWS or any other cloud service. That means each slave needs to transmit its data to its master so that it eventually reaches the top 10 masters who can push it to the cloud.
Now, does mesh network support retransmitting of data or if there's any open-source mesh software that I could use in a situation like this?

Answer 1

Normally, the network stack of the mesh network would handle this. Zigbee is an example of a mesh network and it's spec describes three device types:

Source: Wikipedia Zigbee

Zigbee devices are of three kinds:

Zigbee Coordinator (ZC): The most capable device, the Coordinator forms the root of the network tree and might bridge to other networks. There is precisely one zigbee Coordinator in each network since it is the device that started the network originally (the zigbee LightLink specification also allows operation without a zigbee Coordinator, making it more usable for off-the-shelf home products). It stores information about the network, including acting as the Trust Center & repository for security keys.[32][33]

Zigbee Router (ZR): As well as running an application function, a Router can act as an intermediate router, passing on data from other devices.

Zigbee End Device (ZED): Contains just enough functionality to talk to the parent node (either the Coordinator or a Router); it cannot relay data from other devices. This relationship allows the node to be asleep a significant amount of the time thereby giving long battery life. A ZED requires the least amount of memory, and, therefore, can be less expensive to manufacture than a ZR or ZC.

So, for your situation, you should have several Zigbee End Devices, ten Zigbee routers and a single internet connected Zigbee Coordinator. 
The Wikipedia page notes this open source Zigbee implementation: http://zboss.dsr-wireless.com/