Jens Deppe created GEODE-5042: --------------------------------- Summary: create index produces misleading/scary messages Key: GEODE-5042 URL: https://issues.apache.org/jira/browse/GEODE-5042 Project: Geode Issue Type: Task Components: gfsh Reporter: Jens Deppe
gfsh {{create index}} can produce output like: {noformat} Command: "create index --name=index64717 --expression=region36991.ID --region=region36991" Command completed in 57 ms Output (starts at beginnning of next line), output length is 1504: Member | Status ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- rs-FullRegression-2018-04-07-04-01-04-client-16(dataStoregemfire1_rs-FullRegression-2018-04-07-04-01-04-client-16_11853:11853)<ec><v2>:1030 | Index successfully created rs-FullRegression-2018-04-07-04-01-04-client-16(dataStoregemfire2_rs-FullRegression-2018-04-07-04-01-04-client-16_11866:11866)<ec><v2>:1029 | Index successfully created rs-FullRegression-2018-04-07-04-01-04-client-16(dataStoregemfire3_rs-FullRegression-2018-04-07-04-01-04-client-16_11886:11886)<ec><v2>:1028 | ERROR: Index "index64717" already exists. Create failed due to duplicate definition. rs-FullRegression-2018-04-07-04-01-04-client-16(dataStoregemfire4_rs-FullRegression-2018-04-07-04-01-04-client-16_11911:11911)<ec><v2>:1026 | Index successfully created rs-FullRegression-2018-04-07-04-01-04-client-16(dataStoregemfire5_rs-FullRegression-2018-04-07-04-01-04-client-16_11922:11922)<ec><v2>:1031 | ERROR: Index "index64717" already exists. Create failed due to duplicate name. rs-FullRegression-2018-04-07-04-01-04-client-16(dataStoregemfire6_rs-FullRegression-2018-04-07-04-01-04-client-16_11930:11930)<ec><v2>:1027 | Index successfully created {noformat} For this command, gfsh sends the 'create index' command to every member and then aggregates the result. If the relevant region is partitioned then the underlying create index command is distributed and the above messages are actually OK. If the region is replicated the underlying index creation is not distributed and any failure should actually result in a legitimate command failure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)