You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Houliang Qi (Jira)" <ji...@apache.org> on 2020/04/03 01:55:00 UTC

[jira] [Commented] (IOTDB-574) Specify configuration when start iotdb

    [ https://issues.apache.org/jira/browse/IOTDB-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074196#comment-17074196 ] 

Houliang Qi commented on IOTDB-574:
-----------------------------------

It is better to support both types. For the second option, user can specify  _rpc_port_ on standalone mode and  user can specify _meta_port_, _data_port_ and s_eed_nodes_ on cluster mode

If two options are used simultaneously, the second option overrides the first one.

> Specify configuration when start iotdb
> --------------------------------------
>
>                 Key: IOTDB-574
>                 URL: https://issues.apache.org/jira/browse/IOTDB-574
>             Project: Apache IoTDB
>          Issue Type: New Feature
>            Reporter: Houliang Qi
>            Priority: Major
>
> now when start iotdb, default configuratiuon is used. If user can specify some configurations, it will be more user-friendly, there have two options:
>  # Users can specify another configuration file, iotdb use the new configure file to start; eg: _./start-server.sh -c path/new_iotdb-engine.properties_
>  # Users can specify some configuration items to override the default configuration; eg:  ./start-server.sh -timestamp_precision=ns -rpc_port=6668 -enable_wal=false
>  
> TDEngine only support the first option([https://github.com/taosdata/TDengine]); Influxdb support the second option, but only a few specific options are supported ([https://github.com/influxdata/influxdb]);
> In my opinion, I prefer the first option for the following reasons:
> 1. Users can specify different configuration files according to different use scenarios;
> 2. The description of configuration items can be better described in the configuration file;
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)