You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Yukun Zhou (Jira)" <ji...@apache.org> on 2022/11/18 02:41:00 UTC
[jira] [Commented] (IOTDB-4668) create storage group failed with 303 but it exists at the result of show storage group
[ https://issues.apache.org/jira/browse/IOTDB-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635611#comment-17635611 ]
Yukun Zhou commented on IOTDB-4668:
-----------------------------------
https://github.com/apache/iotdb/pull/8037
> create storage group failed with 303 but it exists at the result of show storage group
> --------------------------------------------------------------------------------------
>
> Key: IOTDB-4668
> URL: https://issues.apache.org/jira/browse/IOTDB-4668
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Schema Manager
> Affects Versions: 0.14.0-SNAPSHOT
> Reporter: changxue
> Assignee: Yukun Zhou
> Priority: Minor
> Labels: pull-request-available
> Attachments: image-2022-10-17-15-32-41-422.png
>
>
> create storage group failed with 303 but it exists at the result of show storage group
> 命令行窗口创建下面值的storage group, 创建后报错303（具体日志信息见附件），但是show storage group 可以看到刚刚创建失败的这个storage group.
>
> storage group:
> root.level2.level3.level4.level5.level6.level7.level8.level9.level10.level11.level12.level13.level14.level15.level16.level17.level18.level19.level20.level21.level22.level23.level24.level25.level26.level27.level28.level29.level30.level31.level32.level33.level34.level35.level36.level37.level38.level39.level40.level41.level42.level43.level44.level45.level46.level47.level48.level49.level50.level51.level52.level53.level54.level55.level56.level57.level58.level59.level60.level61.level62.level63.level64.level65.level66.level67.level68.level69.level70.level71.level72.level73.level74.level75.level76.level77.level78.level79.level80.level81.level82.level83.level84.level85.level86.level87.level88.level89.level90.level91.level92.level93.level94.level95.level96.level97.level98.level99.level100.level101.level102.level103.level104.level105.level106.level107.level108.level109.level110.level111.level112.level113.level114.level115.level116.level117.level118.level119.level120.level121.level122.level123.level124.level125.level126.level127.level128.level129.level130.level131.level132.level133.level134.level135.level136.level137.level138.level139.level140.level141.level142.level143.level144.level145.level146.level147.level148.level149.level150.level151.level152.level153.level154.level155.level156.level157.level158.level159.level160.level161.level162.level163.level164.level165.level166.level167.level168.level169.level170.level171.level172.level173.level174.level175.level176.level177.level178.level179.level180.level181
>
> environment:
> 1. git pull origin master
> 2. mvn clean package -pl server -am -DskipTests
> 3. iotdb/server/target/iotdb-server-0.14.0-SNAPSHOT/sbin/start-server.sh
> 2022-10-17 172.20.70.44
>
> failed info:
> !image-2022-10-17-15-32-41-422.png!
>
> reproduction:
> # build the newest source code of master branch, start-server.sh
> # start-cli.sh
> # show storage group: no such storage group with upstairs value
> # create storage group with the value upstairs, failed
> # show storage group, it shows the storage group with upstairs value
>
> 说明：
> 使用java原生接口测试，发现该问题。
> 然后使用命令行测试，复现。
> 在0.13.3版本上复测，没有该问题。
> *在分布式3C3D上，没有这个问题。可以创建成功，可以查询成功。*
> 建议：
> linux对文件名长度有限制，ext2~ext4是255 bytes, ntfs是255字符。路径长度4096 bytes
> 或许应该全面考虑名称长度问题。可以检查用户指定的data路径，可以限制storage group本身长度等。
--
This message was sent by Atlassian Jira
(v8.20.10#820010)