Closed psam44 closed 1 year ago
Hi @psam44 ,
Which version of Elasticsearch are you using?
version[8.6.0], pid[31684], build[zip/f67ef2df40237445caa70e2fef79471cc608d70d/2023-01-04T09:35:21.782467981Z], OS[Windows 11/10.0/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/19.0.1/19.0.1+10-21]
JVM home [C:\bin\elasticsearch-8.6.0\jdk], using bundled JDK [true] JVM arguments [-Des.networkaddress.cache.ttl=60, -Des.networkaddress.cache.negative.ttl=10, -Djava.security.manager=allow, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j2.formatMsgNoLookups=true, -Djava.locale.providers=SPI,COMPAT, --add-opens=java.base/java.io=ALL-UNNAMED, -XX:+UseG1GC, -Djava.io.tmpdir=C:\Users\Patrick\AppData\Local\Temp\elasticsearch, -XX:+HeapDumpOnOutOfMemoryError, -XX:+ExitOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -Xms16256m, -Xmx16256m, -XX:MaxDirectMemorySize=8522825728, -XX:InitiatingHeapOccupancyPercent=30, -XX:G1ReservePercent=25, -Des.distribution.type=zip, --module-path=C:\bin\elasticsearch-8.6.0\lib, --add-modules=jdk.net, -Djdk.module.main=org.elasticsearch.server]
Package versions: jackson-annotations=2.13.2, jackson-core=2.13.2, jackson-databind=2.13.2.2, jackson-dataformat-xml=2.13.2, jackson-datatype-jsr310=2.13.2, azure-core=1.27.0, Troubleshooting version conflicts: https://aka.ms/azsdk/java/dependency/troubleshoot
It's because we do not support ES 8.6 for now. We officially support the 7.10 (the 7.16 may work as well but I'm cautious since ES do breaking in minor sometimes
Not sure if it's really related but according to this dependency: "@elastic/elasticsearch": "https://github.com/elastic/elasticsearch-js/archive/refs/tags/v7.13.0.tar.gz", I gave preference to a 7.13.4 version and the deletion action is now fine.
console trace: 16:50:01,701 Error: invalid parameter [size], use [max_docs] instead _timeoutRequest kuzzle.js:2 query kuzzle.js:2 query kuzzle.js:2 mDelete kuzzle.js:2 e kuzzleWrapper-v1.ts:115 l runtime.js:63 S runtime.js:293 O runtime.js:118 Babel 4 t kuzzleWrapper-v1.ts:40 i Page.vue:708 l runtime.js:63 S runtime.js:293 O runtime.js:118 Babel 4 onDeleteConfirmed Page.vue:705 VueJS 4 click DeleteModal.vue:3 VueJS 37 mountTarget transporter.js:123 beforeMount transporter.js:89 VueJS 21 onDeleteClicked Page.vue:743 VueJS 4 delete List.vue:1 VueJS 4 deleteDocument DocumentListItem.vue:191 click DocumentListItem.vue:5 VueJS 3
This appends on confirmation of a delete. If it matters, it's a document in the payloads collection of device-manager.
Context (Environment)
Kuzzle version: 2.19.12 Node.js version: 18.13.0 Admin Console version: 4.3.2