[jira] [Assigned] (IOTDB-372) [Distributed] Support node deletion.
[ https://issues.apache.org/jira/browse/IOTDB-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Jiang reassigned IOTDB-372: Assignee: Tian Jiang > [Distributed] Support node deletion. > > > Key: IOTDB-372 > URL: https://issues.apache.org/jira/browse/IOTDB-372 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Tian Jiang >Assignee: Tian Jiang >Priority: Major > Labels: distributed > > Currently, only node addition is supported, to take a step toward scaling > even auto-scaling, node deletion. Node deletion is no simple reversion of > node addition, it should be carefully designed, discussed and verified. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-352) [Distributed] Recognize and skip duplicated files in a snapshot
[ https://issues.apache.org/jira/browse/IOTDB-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Jiang reassigned IOTDB-352: Assignee: Tian Jiang > [Distributed] Recognize and skip duplicated files in a snapshot > --- > > Key: IOTDB-352 > URL: https://issues.apache.org/jira/browse/IOTDB-352 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Tian Jiang >Assignee: Tian Jiang >Priority: Major > Labels: distributed > Attachments: The solution to data deduplication across replicasV1.docx > > > By the naming of TsFiles in IoTDB, the files with the same data may have > different names on different nodes. When such files are sent through > snapshots, the receiver is unable to tell whether the file already exists > locally or not, so it will blindly load the file as an unsequential one (if > it does overlap any existing files), which will waste a lot of system > resources. > How can we figure out if we already have one file or not? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-350) [Distributed] Integrate with time partitioning of data
[ https://issues.apache.org/jira/browse/IOTDB-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Jiang reassigned IOTDB-350: Assignee: Tian Jiang (was: Xiangdong Huang) > [Distributed] Integrate with time partitioning of data > -- > > Key: IOTDB-350 > URL: https://issues.apache.org/jira/browse/IOTDB-350 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Tian Jiang >Assignee: Tian Jiang >Priority: Major > Labels: distributed > > When time partitioning of data is supported in the standalone IoTDB, the > distributed version should integrate with this feature and partition data > using the same granularity as IoTDB's. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-348) [Distributed] Support more non-query operations (log types)
[ https://issues.apache.org/jira/browse/IOTDB-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17067305#comment-17067305 ] Tian Jiang commented on IOTDB-348: -- CRUD -* AggregationPlan- -* BatchInsertPlan- * DeletePlan -* FillQueryPlan- -* GroupByPlan- -* InsertPlan- -* QueryPlan- * UpdatePlan System: * AuthorPlan * CountPlan -* CreateTimeSeries- * DataÅuthPlan * DeleteStorageGroupPlan * DeleteTimeSeriesPlan * LoadConfigurationPlan * LoadDataPlan * OperateFilePlan -* SetStorageGroupPlan- * SetTTLPlan * SHowChildPathsPlan * ShowPlan * ShowTimeSeriesPlan * ShowTTLPlan > [Distributed] Support more non-query operations (log types) > --- > > Key: IOTDB-348 > URL: https://issues.apache.org/jira/browse/IOTDB-348 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Tian Jiang >Priority: Major > Labels: distributed > Attachments: image-2020-01-30-21-18-42-831.png > > > Currently supported operations: > create storage group > create timeseries > single row insertion > Please link to and reply to this issue if you added any new functionalities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-519) Apache IoTDB integration with Prometheus
[ https://issues.apache.org/jira/browse/IOTDB-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066597#comment-17066597 ] Venkat Datta commented on IOTDB-519: Hi [~badrul_c], I'm happy to collaborate with you on building the Prometheus connector. I have interpreted my views in the above comments. I'm currently working on consolidating everything into a single document and share it for a review. > Apache IoTDB integration with Prometheus > > > Key: IOTDB-519 > URL: https://issues.apache.org/jira/browse/IOTDB-519 > Project: Apache IoTDB > Issue Type: Wish > Components: Others >Reporter: Xiangdong Huang >Priority: Major > Labels: gsoc2020, iotdb, mentor > Attachments: image-2020-03-07-15-24-34-192.png, > image-2020-03-07-15-24-51-531.png, image-2020-03-07-15-25-08-037.png > > > IoTDB is a highly efficient time series database. > Prometheus is a monitoring and alerting toolkit, which supports collecting > data from other systems, servers, and IoT devices, saving data into a DB, > visualizing data and provides some query APIs. > > Prometheus allows users to use their database rather than just Prometheus DB > for storing time series databases. > This proposal is for integrating IoTDB with Prometheus. > > You should know: > * How to use Prometheus > * How to use IoTDB > * Java and Go language > difficulty: Major > mentors: > h...@apache.org -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-567) Apache IoTDB's Peer Tracker for The Raft Protocol [distributed]
[ https://issues.apache.org/jira/browse/IOTDB-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066549#comment-17066549 ] Tan xinyu commented on IOTDB-567: - Hello! I'm Tan Xinyu, a senior undergraduate at Software Engineering in Tsinghua University. I'm quite interested in raft peer tracker, and I'm familiar with etcd's implementation about peer tracker. I'd like to try my best in contributing to it. Thanks! > Apache IoTDB's Peer Tracker for The Raft Protocol [distributed] > --- > > Key: IOTDB-567 > URL: https://issues.apache.org/jira/browse/IOTDB-567 > Project: Apache IoTDB > Issue Type: Task > Components: Core/Cluster >Reporter: Xiangdong Huang >Priority: Major > Labels: IoTDB, gsoc2020, mentor > > IoTDB is a highly efficient time-series database, which supports high-speed > query process, including aggregation query. > Currently, clustered IoTDB is under close development. It now supports leader > election, log replication, cluster membership change, and log compaction. We > are testing and optimizing these features these days. > However, we have not yet implemented log status tracking for peers, which > leads to the fact that when sending the logs, the logs required by a peer may > not be immediately sent correctly, resulting in wasted bandwidth and possible > errors. > So there are two improvements about peer tracker need to be done: > 1.implement a peer tracker to track follower's log status. You can borrow > from other projects or design your own, as long as it's right. > 2.you should also dynamically maintain the peer tracker on the current design > and handle possible conflicting inconsistencies, this requires a little > understanding of IoTDB’s raft log module. > This proposal is mainly for implementing and maintaining a peer tracker in > clustered IoTDB. > It is necessary for you to understand that correctness is the most important > thing. > You should know: > - IoTDB cluster structure > - IoTDB raft RPC module > - IoTDB raft log module > - Raft > - Java > difficulty: Major > Mentor: > jt2594...@163.com, h...@apache.org > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-567) Apache IoTDB's Peer Tracker for The Raft Protocol [distributed]
[ https://issues.apache.org/jira/browse/IOTDB-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tan xinyu reassigned IOTDB-567: --- Assignee: Tan xinyu > Apache IoTDB's Peer Tracker for The Raft Protocol [distributed] > --- > > Key: IOTDB-567 > URL: https://issues.apache.org/jira/browse/IOTDB-567 > Project: Apache IoTDB > Issue Type: Task > Components: Core/Cluster >Reporter: Xiangdong Huang >Assignee: Tan xinyu >Priority: Major > Labels: IoTDB, gsoc2020, mentor > > IoTDB is a highly efficient time-series database, which supports high-speed > query process, including aggregation query. > Currently, clustered IoTDB is under close development. It now supports leader > election, log replication, cluster membership change, and log compaction. We > are testing and optimizing these features these days. > However, we have not yet implemented log status tracking for peers, which > leads to the fact that when sending the logs, the logs required by a peer may > not be immediately sent correctly, resulting in wasted bandwidth and possible > errors. > So there are two improvements about peer tracker need to be done: > 1.implement a peer tracker to track follower's log status. You can borrow > from other projects or design your own, as long as it's right. > 2.you should also dynamically maintain the peer tracker on the current design > and handle possible conflicting inconsistencies, this requires a little > understanding of IoTDB’s raft log module. > This proposal is mainly for implementing and maintaining a peer tracker in > clustered IoTDB. > It is necessary for you to understand that correctness is the most important > thing. > You should know: > - IoTDB cluster structure > - IoTDB raft RPC module > - IoTDB raft log module > - Raft > - Java > difficulty: Major > Mentor: > jt2594...@163.com, h...@apache.org > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-519) Apache IoTDB integration with Prometheus
[ https://issues.apache.org/jira/browse/IOTDB-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066450#comment-17066450 ] Badrul Chowdhury commented on IOTDB-519: Hi [~VenkatDatta], I was hoping to work on this for GSoC 2020, here is my proposal: [https://docs.google.com/document/d/1UYOUd0YomS6NUitG9Ko0gqzYapn6eqhFuy_5F3NKVxg/edit?usp=sharing.] I'd be happy to work with you on implementing the connector for Prometheus. If you would rather work on this by yourself, I can pivot to a different connector too. Either way, please let me know! Thanks, Badrul > Apache IoTDB integration with Prometheus > > > Key: IOTDB-519 > URL: https://issues.apache.org/jira/browse/IOTDB-519 > Project: Apache IoTDB > Issue Type: Wish > Components: Others >Reporter: Xiangdong Huang >Priority: Major > Labels: gsoc2020, iotdb, mentor > Attachments: image-2020-03-07-15-24-34-192.png, > image-2020-03-07-15-24-51-531.png, image-2020-03-07-15-25-08-037.png > > > IoTDB is a highly efficient time series database. > Prometheus is a monitoring and alerting toolkit, which supports collecting > data from other systems, servers, and IoT devices, saving data into a DB, > visualizing data and provides some query APIs. > > Prometheus allows users to use their database rather than just Prometheus DB > for storing time series databases. > This proposal is for integrating IoTDB with Prometheus. > > You should know: > * How to use Prometheus > * How to use IoTDB > * Java and Go language > difficulty: Major > mentors: > h...@apache.org -- This message was sent by Atlassian Jira (v8.3.4#803005)
