Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Hi, IoTDB only supports stand-alone version now. We plan to develop distributed version in next two months.
We initially decided to use the master-slave architecture. The master node is responsible for processing read and write requests, and the slave node is responsible for processing read-only requests as a copy.
In terms of implementation, we currently intend to use the raft protocol to ensure the data consistency of each replica node.
If you have any suggestion, please comment below or send an email to our mailing list(dev@iotdb.apache.org).
Attachments
Issue Links
- Blocked
-
IOTDB-781 [Distributed]Support AlterTimeSeriesPlan in distributed version
- Closed
-
IOTDB-1182 [Distributed] read and write in leader node
- Open
-
IOTDB-1251 optimization route intervals
- Closed
- is a parent of
-
IOTDB-373 [Distributed] Query coordinating
- Open
-
IOTDB-1302 [Distributed] Remove what is not in the snapshot during installation
- Open
-
IOTDB-674 [Distributed] WAL cannot be replayed due to meta missing
- Closed
-
IOTDB-823 [Distributed] All Nodes Report Successful Execution When Delete Timeseries Simultaneously
- Closed
-
IOTDB-896 [Distributed] Fail to Insert Nonexistent Timeseries
- Closed
-
IOTDB-917 [Distributed] Prevent rebooting from damaging file versions
- Closed
-
IOTDB-1096 [Distributed]Can not restart the servers when added one new node
- Closed
-
IOTDB-1402 Support the auto-create-schema mechanism for insertRecords in cluster module
- Closed
-
IOTDB-1404 Write blocking problem for three node three replica cluster
- Closed
-
IOTDB-838 [Distributed]merge raft log and wal log
- Open
-
IOTDB-857 [Distributed]make call traceable
- Open
-
IOTDB-992 [Distributed] The ability to migrate stand-alone version data to distributed version
- Open
-
IOTDB-801 [Distributed]Separate data port and heartbeat port
- Resolved
-
IOTDB-372 [Distributed] Support node deletion.
- Closed
-
IOTDB-925 [Distributed]Add a mechanism for detecting down nodes
- Closed
-
IOTDB-688 [Distributed] Supplement the functionalities of NodeTool
- Open
-
IOTDB-690 [Distributed] Turn to broadcasting when calculating targeting nodes takes too long
- Open
-
IOTDB-820 [Distributed] A non-blocking snapshot should be brought up
- Open
-
IOTDB-854 [Distributed] Limit the memory foorprint of the committed log cache
- Open
-
IOTDB-880 [Distributed] Better concurrecy control in RaftLogManager
- Open
-
IOTDB-998 [Distributed] Split the snapshot when sending to follower
- Open
-
IOTDB-1019 [Distributed] Memory control of the cluster engine
- Open
-
IOTDB-1020 [Distributed] Split the persist log buffer to better absorb ingestion
- Open
-
IOTDB-1236 Improve jdbc performance for creating timeseries in cluster module
- Open
-
IOTDB-1370 Cache Leader feature Optimization for massive device scenarios
- Open
-
IOTDB-349 [Distributed] Incrementally update snapshot
- Open
-
IOTDB-353 [Distributed] Validate files in snapshots
- Open
-
IOTDB-900 [Distributed] Tree-structured log forwarding within a raft group.
- Open
-
IOTDB-821 [Distributed] Flush Raft Logs in Batches
- Resolved
-
IOTDB-822 [Distributed] Flush Raft Logs Periodically
- Resolved
-
IOTDB-1118 [Distributed] Limit query log lag in mid consistency level
- Resolved
-
IOTDB-814 [Distributed] Cache and redirect distributed IoTDB's leader for write requests in IoTDB's client
- Resolved
-
IOTDB-815 [Distributed] Support cluster_name check
- Resolved
-
IOTDB-348 [Distributed] Support more non-query operations (log types)
- Closed
-
IOTDB-350 [Distributed] Integrate with time partitioning of data
- Closed
-
IOTDB-351 [Distributed] Serialize the raft logs
- Closed
-
IOTDB-352 [Distributed] Recognize and skip duplicated files in a snapshot
- Closed
-
IOTDB-355 [Distributed] Start-up checks
- Closed
-
IOTDB-451 [Distributed]Recovery of snapshot pulling
- Closed
-
IOTDB-460 [Distributed] Remove data of outdated slots
- Closed
-
IOTDB-526 [Distributed] Support metadata queries
- Closed
-
IOTDB-532 [Distributed] Enabling parallel processing within a data group
- Closed
-
IOTDB-554 [Distributed] Add the ability to resolve log inconsistencies for AppendEntries request
- Closed
-
IOTDB-555 [Distributed] Add peer tracker
- Closed
-
IOTDB-556 [Distributed] Implement truncate function for logs inconsistence
- Closed
-
IOTDB-562 [Distributed]Apache IoTDB raft log persistence in the distributed version
- Closed
-
IOTDB-568 [Distributed] Protect files of data snapshot
- Closed
-
IOTDB-590 [Distributed] add other meta data when do metaSnapshot
- Closed
-
IOTDB-601 [Distributed]Add authentication in MetaSnapshot
- Closed
-
IOTDB-602 [Distributed] Check or enable LAST query
- Closed
-
IOTDB-604 [Distributed] More robust cluster readers
- Closed
-
IOTDB-606 [Distributed] Replace raw logs in MetaSnapshot
- Closed
-
IOTDB-709 [Distributed] Enable schema auto-creation
- Closed
-
IOTDB-722 [Distributed] Support mode consistencies
- Closed
-
IOTDB-723 [Distributed] Decide a log discarding policy
- Closed
-
IOTDB-807 [Distributed]Make heartbeat thread commit log asynchronous
- Closed
-
IOTDB-809 [Distributed] Separate Read and Write Timeout Threshold Configurations
- Closed
-
IOTDB-810 [Distributed] Set Configuration of Max Number of Logs in Memory
- Closed
-
IOTDB-860 [Distributed]Emend the async log applier
- Closed
-
IOTDB-884 [Distributed] Batched forwarding for batched requests
- Closed
-
IOTDB-915 [Distributed] Merge StableEntryManager into CommittedLogManager
- Closed
-
IOTDB-918 [Distributed] Bind TsFiles with log index to accelerate snapshots
- Closed
-
IOTDB-948 [Distributed]Use binary search when checking the follower's match index when catchup
- Closed
-
IOTDB-953 [Distributed] Improve handling when a node cannot be reached
- Closed
-
IOTDB-1099 Optimize insertablets logic in cluster module
- Closed
-
IOTDB-1117 [Distributed] Batched creation and fetch of RemoteSeriesReader
- Closed
-
IOTDB-1399 Make session and jdbc interface more adaptable to the cluster
- Closed
-
IOTDB-354 [Distributed] Implement batch append entries
- Closed
-
IOTDB-586 [Distributed] Eliminate some timeseries schemas When memory is limited
- Closed
-
IOTDB-613 [Distributed] Add the ability to persist and maintain currentterm for the raft node
- Closed
-
IOTDB-620 [Distributed] Add the ability to persist and maintain voteFor for the raft node and amend the judgment conditions for elections
- Closed
-
IOTDB-571 [Distributed] Automated cluster test
- Open
-
IOTDB-858 [Distributed]Add cluster setup document
- Closed
-
IOTDB-567 [Distributed]Apache IoTDB's Peer Tracker for The Raft Protocol
- Closed
- relates to
-
IOTDB-1218 [Distributed]System properties is not persist in cluster version
- Closed
- links to
1.
|
[Distributed] Query coordinating | Open | Unassigned | |
2.
|
[Distributed] Incorrect Snapshot implementation and LogManager | Closed | Unassigned |