Uploaded image for project: 'Apache IoTDB'
  1. Apache IoTDB
  2. IOTDB-5143

Create aligned timeseries about 3W sensors with benchmark, only schema regions are created, data regions are empty

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Cannot Reproduce
    • 1.0.0
    • None
    • Core/Server
    • None
    • 2023-1-ConfigNode

    Description

      【2023.1.3 comments:There are not any usefully logs, need reproduce in 1.0.1 branch.】

       

      environment:
      3C3D cluster, master Dec.8th source codes
      iot-benchmark 1.0 is OK

      reproduction:
      1. run iot-benchmark with 1 device 30 thousands sensors, configs see attachment config.properties
      2. the benchmark logs show

      2022-12-08 11:09:54,288 WARN  org.apache.iotdb.tsfile.common.conf.TSFileDescriptor:132 - not found iotdb-common.properties, use the default configs.
      

      This message also shows in confignode logs.

      benchmark configuration see attachment of config.properties, using 1.0

      问题:
      没有任何数据写入:show regions只显示schema region的信息,没有data region的

      Attachments

        1. _allnodes-log.tar.gz
          81 kB
          changxue
        2. benchmark-log.out
          18 kB
          changxue
        3. config.properties
          15 kB
          changxue
        4. IOTDB-5143_allnodes-log.tar.gz
          93 kB
          changxue

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            caogaofei Gaofei Cao Assign to me
            changxue changxue
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Agile

                Completed Sprint:
                2023-1-ConfigNode ended 02/Feb/23
                View on Board

                Slack

                  Issue deployment