Jatin Kumar
08/07/2022, 1:43 PMparticipant
folder from zookeeper in latest release?Stuart Millholland
08/07/2022, 3:23 PMEthan Huang
08/08/2022, 7:38 AMharnoor
08/08/2022, 5:49 PMRelocation failed for table
as segments are in error state.
We have used the Reset API for all the segments which were in BAD state.
But trying to understand why this error occurs? (No table config change was made from our end and segments were being relocated successfully earlier).
2022/08/08 16:22:18.328 INFO [PinotLLCRealtimeSegmentManager] [grizzly-http-server-1] Committing segment metadata for segment: span_event_view_1__91__4093__20220808T1558Z
--
java.lang.IllegalStateException: Found segments in ERROR state
at org.apache.pinot.controller.helix.core.rebalance.TableRebalancer.isExternalViewConverged(TableRebalancer.java:556) ~[pinot-all-0.9.1-jar-with-dependencies.jar:0.9.1-f8ec6f6f8eead03488d3f4d0b9501fc3c4232961]
at org.apache.pinot.controller.helix.core.rebalance.TableRebalancer.waitForExternalViewToConverge(TableRebalancer.java:498) ~[pinot-all-0.9.1-jar-with-dependencies.jar:0.9.1-f8ec6f6f8eead03488d3f4d0b9501fc3c4232961]
at org.apache.pinot.controller.helix.core.rebalance.TableRebalancer.rebalance(TableRebalancer.java:361) ~[pinot-all-0.9.1-jar-with-dependencies.jar:0.9.1-f8ec6f6f8eead03488d3f4d0b9501fc3c4232961]
at org.apache.pinot.controller.helix.core.relocation.SegmentRelocator.lambda$processTable$0(SegmentRelocator.java:96) ~[pinot-all-0.9.1-jar-with-dependencies.jar:0.9.1-f8ec6f6f8eead03488d3f4d0b9501fc3c4232961]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
2022/08/08 17:10:25.590 ERROR [SegmentRelocator] [restapi-multiget-thread-2037] Relocation failed for table: span_event_view_1_REALTIME
Luis Fernandez
08/08/2022, 6:27 PMSukesh Boggavarapu
08/08/2022, 7:04 PMSukesh Boggavarapu
08/08/2022, 7:04 PMaged/pinot-pinot-broker-1[broker]: 2022/08/08 19:03:22.866 ERROR [PinotClientRequest] [jersey-server-managed-async-executor-2] Caught exception while processing POST request
managed/pinot-pinot-broker-1[broker]: java.lang.IllegalArgumentException: Unsupported function: lookup not found
managed/pinot-pinot-broker-1[broker]: at org.apache.pinot.core.query.postaggregation.PostAggregationFunction.<init>(PostAggregationFunction.java:47) ~[startree-pinot-all-0.11.0-ST.23-jar-with-dependencies.jar:0.11.0-ST.23-f32ac7b496c8e8576415b40228127b5c64ead9fc]
managed/pinot-pinot-broker-1[broker]: at org.apache.pinot.core.query.reduce.PostAggregationHandler$PostAggregationValueExtractor.<init>(PostAggregationHandler.java:164) ~[startree-pinot-all-0.11.0-ST.23-jar-with-dependencies.jar:0.11.0-ST.23-f32ac7b496c8e8576415b40228127b5c64ead9fc]
managed/pinot-pinot-broker-1[broker]: at org.apache.pinot.core.query.reduce.PostAggregationHandler.getValueExtractor(PostAggregationHandler.java:136) ~[startree-pinot-all-0.11.0-ST.23-jar-with-dependencies.jar:0.11.0-ST.23-f32ac7b496c8e8576415b40228127b5c64ead9fc]
managed/pinot-pinot-broker-1[broker]: at org.apache.pinot.core.query.reduce.PostAggregationHandler.<init>(PostAggregationHandler.java:77) ~[startree-pinot-all-0.11.0-ST.23-jar-with-dependencies.jar:0.11.0-ST.23-f32ac7b496c8e8576415b40228127b5c64ead9fc]
managed/pinot-pinot-broker-1[broker]: at org.apache.pinot.core.query.reduce.GroupByDataTableReducer.reduceToResultTable(GroupByDataTableReducer.java:133) ~[startree-pinot-all-0.11.0-ST.23-jar-with-
Gerrit van Doorn
08/08/2022, 8:07 PMAnkit Sultana
08/08/2022, 8:26 PM"ingestionConfig": {
"transformConfigs": [{
"columnName": "timestamp_start_int",
"transformFunction": "cast(\"timestamp_start\", \"LONG\")"
}]
},
Sukesh Boggavarapu
08/08/2022, 11:00 PMTanmesh Mishra
08/09/2022, 2:19 AMAlice
08/09/2022, 7:18 AM2022/08/09 03:00:48.603 ERROR [LLRealtimeSegmentDataManager_table_stage__2__0__20220809T0117Z] [table_stage__2__0__20220809T0117Z] Could not build segment
java.lang.IllegalArgumentException: integer overflow detected
at org.apache.pinot.shaded.com.google.common.base.Preconditions.checkArgument(Preconditions.java:122) ~[pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.segment.local.segment.creator.impl.fwd.MultiValueVarByteRawIndexCreator.<init>(MultiValueVarByteRawIndexCreator.java:80) ~[pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.segment.local.segment.creator.impl.DefaultIndexCreatorProvider.getRawIndexCreatorForMVColumn(DefaultIndexCreatorProvider.java:251) ~[pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.segment.local.segment.creator.impl.DefaultIndexCreatorProvider.newForwardIndexCreator(DefaultIndexCreatorProvider.java:85) ~[pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.segment.spi.index.IndexingOverrides$Default.newForwardIndexCreator(IndexingOverrides.java:156) ~[pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.segment.local.segment.creator.impl.SegmentColumnarIndexCreator.init(SegmentColumnarIndexCreator.java:215) ~[pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.segment.local.segment.creator.impl.SegmentIndexCreationDriverImpl.build(SegmentIndexCreationDriverImpl.java:216) ~[pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.segment.local.realtime.converter.RealtimeSegmentConverter.build(RealtimeSegmentConverter.java:123) ~[pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.core.data.manager.realtime.LLRealtimeSegmentDataManager.buildSegmentInternal(LLRealtimeSegmentDataManager.java:873) [pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.core.data.manager.realtime.LLRealtimeSegmentDataManager.buildSegmentForCommit(LLRealtimeSegmentDataManager.java:800) [pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at org.apache.pinot.core.data.manager.realtime.LLRealtimeSegmentDataManager$PartitionConsumer.run(LLRealtimeSegmentDataManager.java:699) [pinot-all-0.11.0-SNAPSHOT-jar-with-dependencies.jar:0.11.0-SNAPSHOT-b58810ccf2c7d18693d01688769dcccd3e761d4b]
at java.lang.Thread.run(Thread.java:829) [?:?]
2022/08/09 03:00:48.607 ERROR [LLRealtimeSegmentDataManager_table_stage__2__0__20220809T0117Z] [table_stage__2__0__20220809T0117Z] Could not build segment for table_stage__2__0__20220809T0117Z
James Kelleher
08/09/2022, 8:44 PMhelm install pinot pinot/pinot
. This worked great, I was even able to set up my own Realtime table consuming from one of our Confluent Kafka queues. Now, I want to play around on a beefier deployment, so I cloned the Helm charts into my own repo. I can still helm install
these, but when I try to create the table, I get this error:
│ 2022/08/09 20:42:54.461 INFO [AddTableCommand] [main] Executing command: AddTable -tableConfigFile /var/pinot/dmp/dmp_realtime_table_config.json -schemaFile /var/pinot/dmp/dmp_realtime_schema.json -co │
│ 2022/08/09 20:42:55.238 INFO [AddTableCommand] [main] {"code":500,"error":"org.apache.pinot.shaded.org.apache.kafka.common.KafkaException: Failed to construct kafka consumer"} │
│ Stream closed EOF for pinot/dmp-job-zhb2d (pinot-add-dmp-json)
Why isn’t Pinot able to construct the Kafka consumer anymore? Am I not deploying two near-identical setups?suraj sheshadri
08/10/2022, 4:12 AMMathieu Alexandre
08/10/2022, 10:58 AMUnable to get consuming segments info from all the servers. Reason: nullI've some segments that persist in OFFLINE even if a reset or reload them. The segment metadatas seems to be stuck with the status "IN_PROGRESS". Does anyone have any ideas on how to handle this situation ?
Ryan Ruane
08/10/2022, 3:42 PMecho srvr | nc localhost 2181
Zookeeper version: 3.5.8-f439ca583e70862c3068a1f2a7d4d068eec33315, built on 05/04/2020 15:53 GMT
Latency min/avg/max: 0/0/20
Received: 5590
Sent: 5751
Connections: 7
Outstanding: 0
Zxid: 0x176
Mode: standalone
Node count: 80
And from there using the following command to ensure the correct number of brokers controllers and servers exist
docker exec -it <container> bin/pinot-admin.sh ShowClusterInfo -clusterName PinotCluster -zkAddress localhost:2181
_brokerInfoList:
- _name: Broker_172.28.0.5_8099
_state: ONLINE
_tags: [DefaultTenant_BROKER]
_clusterName: PinotCluster
_controllerInfo: {_leaderName: 172.28.0.3_9000}
_serverInfoList:
- _name: Server_172.28.0.4_8098
_state: ONLINE
_tags: [DefaultTenant_OFFLINE, DefaultTenant_REALTIME]
_tableInfoList:
- _segmentInfoList:
- _name: cases_OFFLINE_20150105_20150106_0
_segmentStateMap: {Server_172.28.0.4_8098: ONLINE}
_tableName: cases_OFFLINE
_tag: cases_OFFLINE
Still, I don't know if this command will produce instances before they are fully ready. I was hoping there was a more direct way to probe each instance individually. Any suggestions would be greatly welcomed.Alice
08/11/2022, 2:59 AMTony Zhang
08/11/2022, 5:28 AMSevvy Yusuf
08/11/2022, 2:49 PM{
"code": 500,
"error": "Specified EXTERNALVIEW the_specified_table_REALTIME is not found!"
}
Can someone advise on why this is? This is only in our staging environment and there is currently no data in this table. How do we fix the state? Thanks in advanceLuis Fernandez
08/11/2022, 3:48 PMScott deRegt
08/11/2022, 4:16 PMorg.apache.spark.SparkException
in our ingestion job which leads to staging segments being purged and no output in outputDirURI
.
See this error in logs, ERROR [LaunchDataIngestionJobCommand] [Driver] Got exception to kick off standalone data ingestion job
,
but Spark application exits as success, INFO [ApplicationMaster] [Driver] Final app status: SUCCEEDED, exitCode: 0
Alice
08/11/2022, 4:19 PMThere are 45 invalid segment/s. This usually means that they were created with an older schema. Please reload the table in order to refresh these segments to the new schema.
Timothy James
08/11/2022, 11:05 PMselect count(*)
is not changing, even though in our own logs we see
Successfully uploaded segment: simple_0_443 of table: simple_OFFLINE
and logging that shows us >0 record count values for each segment . It was working before (that is, before I turned on pinot controller auth), as is stuck at 757051
count and 7653
segments.
How is this even possible? I've tried reloading all segments for the table. Help?Hassan Ait Brik
08/12/2022, 9:04 AM2022/08/12 08:19:44.332 WARN [ZkBaseDataAccessor] [ZkClient-EventThread-62-pinot-zookeeper:2181] Fail to read record for paths: {/pinot/INSTANCES/Server_pinot-server-0.pinot-server-headless.data.svc.cluster.local_8098/MESSAGES/6549d816-93d8-42a0-8476-b636e2e1566b=-101, /pinot/INSTANCES/Server_pinot-server-0.pinot-server-headless.data.svc.cluster.local_8098/MESSAGES/37d924db-e540-4f87-b300-9e17bfe7d0db=-101}
Hassan Ait Brik
08/12/2022, 9:04 AM[
{
"message": "java.net.UnknownHostException: pinot-server-0.pinot-server-headless.data.svc.cluster.local\n\tat java.base/java.net.InetAddress$CachedAddresses.get(InetAddress.java:797)\n\tat java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1509)\n\tat java.base/java.net.InetAddress.getAllByName(InetAddress.java:1368)\n\tat java.base/java.net.InetAddress.getAllByName(InetAddress.java:1302)",
"errorCode": 425
},
{
"message": "2 servers [pinot-server-0_O, pinot-server-2_O] not responded",
"errorCode": 427
}
]
for some reason pinot-server-0 is not responded (it seems to be in a "bad phase" from yesterday 6pm)
it seems to have a recurring problem - As if it were "restarting again and again"Hassan Ait Brik
08/12/2022, 2:20 PMBruno Mendes
08/12/2022, 10:20 PMTony Zhang
08/12/2022, 11:20 PMPrashant Pandey
08/13/2022, 4:20 AMInput Partitions: 96
Average Ingestion Rate (30 days): 154k
Max Ingestion Rate (30 days): 390k (spike)
Avg. ingestion rate / partitions ~2000 (200,000 / 96 with some buffer)
Retention Hours (on realtime servers): 1h, segments are relocated post this to OFFLINE servers.
Max Usable Host Memory: 100G (128G total, 28G for query processing)
Most Queried Time Interval: 1h (hence retention = 1h)
Command:
./pinot-admin.sh RealtimeProvisioningHelper -tableConfigFile /var/pinot/tableConfig.json -sampleCompletedSegmentDir /var/pinot/mySegment/ -numPartitions 96 -numHosts 4,6,8,10,12 -numHours 1 -ingestionRate 2000 -maxUsableHostMemory 100G -retentionHours 1
Results:
numHosts --> 4 |6 |8 |10 |12 |
numHours
1 --------> 46.53G/46.53G |31.02G/31.02G |23.26G/23.26G |19.39G/19.39G |15.51G/15.51G |
numHosts --> 4 |6 |8 |10 |12 |
numHours
1 --------> 1.68G |1.68G |1.68G |1.68G |1.68G |
numHosts --> 4 |6 |8 |10 |12 |
numHours
1 --------> 46.53G |31.02G |23.26G |19.39G |15.51G |
numHosts --> 4 |6 |8 |10 |12 |
numHours
1 --------> 24 |16 |12 |10 |8 |
Wanted to understand why is memory being mapped when total consuming memory + mapped memory < total memory available for ingestion in all the four cases?Alice
08/15/2022, 2:10 AM