WARNING: All illegal access operations will be denied in a future release Exception in thread "main" java.lang.NoSuchMethodError: 'org.apache.htrace.HTraceConfiguration org.apache.hadoop.tracing.TraceUtils.wrapHadoopConf(org.apache.hadoop.conf.Configuration)' at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:635) at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:619) at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:149) at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2812) at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:100) at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2849) at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2831) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:389) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:181) at org.apache.pinot.plugin.filesystem.HadoopPinotFS.init(HadoopPinotFS.java:65) at org.apache.pinot.spi.filesystem.PinotFSFactory.register(PinotFSFactory.java:52) at org.apache.pinot.spi.filesystem.PinotFSFactory.init(PinotFSFactory.java:72) at org.apache.pinot.controller.BaseControllerStarter.initPinotFSFactory(BaseControllerStarter.java:518) at org.apache.pinot.controller.BaseControllerStarter.setUpPinotController(BaseControllerStarter.java:358) at org.apache.pinot.controller.BaseControllerStarter.start(BaseControllerStarter.java:308) at org.apache.pinot.tools.service.PinotServiceManager.startController(PinotServiceManager.java:123) at org.apache.pinot.tools.service.PinotServiceManager.startRole(PinotServiceManager.java:93) at org.apache.pinot.tools.admin.command.StartServiceManagerCommand.lambda$startBootstrapServices$0(StartServiceManagerCommand.java:233) at org.apache.pinot.tools.admin.command.StartServiceManagerCommand.startPinotService(StartServiceManagerCommand.java:285) at org.apache.pinot.tools.admin.command.StartServiceManagerCommand.startBootstrapServices(StartServiceManagerCommand.java:232) at org.apache.pinot.tools.admin.command.StartServiceManagerCommand.execute(StartServiceManagerCommand.java:182) at org.apache.pinot.tools.admin.command.StartControllerCommand.execute(StartControllerCommand.java:149) at org.apache.pinot.tools.admin.PinotAdministrator.execute(PinotAdministrator.java:166) at org.apache.pinot.tools.admin.PinotAdministrator.main(PinotAdministrator.java:186) at org.apache.pinot.tools.admin.PinotController.main(PinotController.java:35)

iam getting above exception while starting up controller using hdfs as deepstore

export HADOOP_HOME=/home/sas/zohohadoop/hdfs export HADOOP_VERSION=2.8.5 export HADOOP_GUAVA_VERSION=11.0.2 export HADOOP_GSON_VERSION=2.2.4 #export GC_LOG_LOCATION=/path/to/gc/log/file export PINOT_VERSION=0.8.0 export PINOT_DISTRIBUTION_DIR=/home/sas/pinot/ export SERVER_CONF_DIR=/home/sas/pinot/conf/ export ZOOKEEPER_ADDRESS=localhost:2191 export CLASSPATH_PREFIX="${HADOOP_HOME}/lib/hadoop-hdfs-${HADOOP_VERSION}.jar:${HADOOP_HOME}/lib/hadoop-annotations-${HADOOP_VERSION}.jar:${HADOOP_HOME}/lib/hadoop-auth-${HADOOP_VERSION}.jar:${HADOOP_HOME}/lib/hadoop-common-${HADOOP_VERSION}.jar:${HADOOP_HOME}/lib/guava-${HADOOP_GUAVA_VERSION}.jar:${HADOOP_HOME}/lib/gson-${HADOOP_GSON_VERSION}.jar:${HADOOP_HOME}/lib/htrace-core4-4.0.1-incubating.jar" export JAVA_OPTS="-Xms4G -Xmx4G" ${PINOT_DISTRIBUTION_DIR}/bin/start-controller.sh -configFileName ${SERVER_CONF_DIR}/controller.conf

using above config

can someone help?

@Xiang Fu @Neha Pawar @Mayank

Hi @Mayank @Xiang Fu @Jackie @Subbu Subramaniam @Kishore G @Daniel Lavoie @Neha Pawar @Kulbir Nijjer.. we are getting following error and broker missing error is coming on pinot sql query editor Ui .. also broker pods are in crashloopbackoff state and are not ready .. please find attached logs of broker pods.. cc : @Mohamed Kashifuddin @Shailesh Jha @Mohamed Sultan @Arun Kumar

Issue: Multiple issues seen with Pinot 0.8 integration with Prestosql350 (Trino). 1. Selecting Boolean col in the projection list is a problem for both real-time, offline tables. Query throws select hasVideo from table1 limit 10; Query 20210901_071343_00190_p5w66 failed: Unable to create class org.apache.pinot.common.response.broker.BrokerResponseNative from JSON response: [{"resultTable":{"dataSchema":{"columnNames":["hasVideo"],"columnDataTypes":["BOOLEAN"]},"rows":[[false],[false],[false],[false],[false],[false],[false],[false],[true],[false]]},"exceptions":[],"numServersQueried":7,"numServersResponded":7,"numSegmentsQueried":7,"numSegmentsProcessed":7,"numSegmentsMatched":7,"numConsumingSegmentsQueried":0,"numDocsScanned":70,"numEntriesScannedInFilter":0,"numEntriesScannedPostFilter":70,"numGroupsLimitReached":false,"totalDocs":70000,"timeUsedMs":5,"offlineThreadCpuTimeNs":3468272,"realtimeThreadCpuTimeNs":0,"segmentStatistics":[],"traceInfo":{},"numRowsResultSet":10,"minConsumingFreshnessTimeMs":0}] 2. Queries not working as expected for DateTime col Pinot does not have a direct DATETIME datatype and supports STRING, LONG, INT via dateTimeFieldSpecs. Now we have a STRING col in dateTimeFieldSpecs section but when using this col to query via prestosql, it's not working as expected. 3. Alias feature is not working. Executed a count() AS total_calls but resultset shows col name as count() only. Alias flow is not taking effect. P.S: We would be raising these concerns with Trino community but thought of sharing it here too.

@Elon @Xiang Fu ^^

Thanks for sharing Vibhor.. some of these might be related to connector as well.

This is fixed in the new version of the connector which will support pinot 0.8.0, aliases, boolean types and more function calls as well.

Already have it working locally, should be soon.

Hi @Elon, can you point me to the link where I could try it? I'm assuming its not officially out.

Right, still working on it and will push it soon, I'll keep you updated.

joined #C011C9JHN7R

We had a previous issue with failed s3 downloads, where the suggested fix was calling the controller endpoint

/segments/{table}/{segment}/reset

. This works in most cases, we were scripting around this problem, but some segments still get stuck in offline state after calling the reset endpoint. I've noticed that these segments are listed under

HELIX_DISABLED_PARTITION

on the server. How can we recover these segments to online state? (running 0.7.1)

Getting the following exceptions when try to upgrade to 0.8, its complaining for found instance name with the same host name:

Exception when connecting the instance Controller_pinot-controller-0.pinot-controller-headless.pinot.svc.cluster.local_9000 as Participant role to Helix.
org.apache.helix.HelixException: instance: Controller_pinot-controller-0.pinot-controller-headless.pinot.svc.cluster.local_9000 already has a live-instance in cluster pinot
	at org.apache.helix.manager.zk.ParticipantManager.createLiveInstance(ParticipantManager.java:251) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.helix.manager.zk.ParticipantManager.handleNewSession(ParticipantManager.java:115) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.helix.manager.zk.ZKHelixManager.handleNewSessionAsParticipant(ZKHelixManager.java:1171) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.helix.manager.zk.ZKHelixManager.handleNewSession(ZKHelixManager.java:1131) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.helix.manager.zk.ZKHelixManager.createClient(ZKHelixManager.java:701) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.helix.manager.zk.ZKHelixManager.connect(ZKHelixManager.java:738) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.controller.ControllerStarter.registerAndConnectAsHelixParticipant(ControllerStarter.java:524) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.controller.ControllerStarter.setUpPinotController(ControllerStarter.java:343) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.controller.ControllerStarter.start(ControllerStarter.java:287) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.tools.service.PinotServiceManager.startController(PinotServiceManager.java:116) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.tools.service.PinotServiceManager.startRole(PinotServiceManager.java:91) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.tools.admin.command.StartServiceManagerCommand.lambda$startBootstrapServices$0(StartServiceManagerCommand.java:234) ~[pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.tools.admin.command.StartServiceManagerCommand.startPinotService(StartServiceManagerCommand.java:286) [pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.tools.admin.command.StartServiceManagerCommand.startBootstrapServices(StartServiceManagerCommand.java:233) [pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.tools.admin.command.StartServiceManagerCommand.execute(StartServiceManagerCommand.java:183) [pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.tools.admin.command.StartControllerCommand.execute(StartControllerCommand.java:130) [pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.tools.admin.PinotAdministrator.execute(PinotAdministrator.java:164) [pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]
	at org.apache.pinot.tools.admin.PinotAdministrator.main(PinotAdministrator.java:184) [pinot-all-0.7.0-SNAPSHOT-jar-with-dependencies.jar:0.7.0-SNAPSHOT-255202ec4fc7df2283f7c275d8e9025a26cf3274]

Hi everyone , In pinot-0.8.0 , i have added controller.task.frequencyPeriod=4h in controller config. and it is working fine in local setup on machine. While in using kubernetes , it gives

image.png

2021-09-03 13_32_01-Clipboard.png

also having an issue that the disk space size is not being reported

2021-09-03 13_32_54-Window.png

always shows -1 doe both the sizes ...

<!here> we are trying to configure s3 as deep storage based on this document https://apache-pinot.slack.com/archives/C011C9JHN7R/p1631221839183400

@Pavel Vaysberg has left the channel

Do we have any way to control skipUpsert when using presto on top of pinot?

Also a lot of

Query scheduling took 12916ms (longer than query timeout of 9999ms)

https://apache-pinot.slack.com/archives/C011C9JHN7R/p1629474594406300?thread_ts=1629472715.403600&amp;cid=C011C9JHN7R Got the same issue. I’m workaround by using jars upload on gcs but it’s doesn’t work. Any idea ?

Hi team - we are using

Upsert

to do some use cases, and I found that there will be a large size map

_primaryKeyToRecordLocationMap

in Pinot server, A partition of an instance can reach tens of millions of data. Seems this map can only release some keys when the old segment destroy. Can we consider adding some strategies to expire keys by time, because most of the data will not be updated after a period of time. Just a suggestion.