#general
@azomshahriar05: @azomshahriar05 has joined the channel
@ruslanrodriquez: @ruslanrodriquez has joined the channel
@liranbri: @liranbri has joined the channel
@liranbri: Hi everyone, In the homepage you wrote that the db is suitable when working on immutable data. However, I do see that you support upserts as well.
@g.kishore: That’s right. Pinot supports upserts use cases.. we will fix the docs
@mayanks: Hello, yes upsert is a recent feature addition.
@liranbri: :pray:
@suresh.swaminathan69: @suresh.swaminathan69 has joined the channel
#random
@azomshahriar05: @azomshahriar05 has joined the channel
@ruslanrodriquez: @ruslanrodriquez has joined the channel
@liranbri: @liranbri has joined the channel
@suresh.swaminathan69: @suresh.swaminathan69 has joined the channel
#troubleshooting
@azomshahriar05: @azomshahriar05 has joined the channel
@ruslanrodriquez: @ruslanrodriquez has joined the channel
@liranbri: @liranbri has joined the channel
@fritzbx: Hi All, I need help with kubernetes installation. I helm install pinot using the chart included in main pinot github (by cloning the entire pinot source code). Apparently broker-0 could not able to come up because of `Cluster structure is not set up for cluster: pinot-quickstart` What went wrong here ? ```cd incubator-pinot/kubernetes/helm/pinot helm install -n pinot-quickstart2 pinot .``` ```Session establishment complete on server pinot-zookeeper/172.20.47.166:2181, sessionid = 0x1012fddef2b0003, negotiated timeout = 30000 zookeeper state changed (SyncConnected) MBean HelixZkClient:Key=pinot-quickstart.Broker_pinot-broker-0.pinot-broker-headless.pinot-quickstart2.svc.cluster.local_8099,Type=SPECTATOR has been registered. MBean HelixZkClient:Key=pinot-quickstart.Broker_pinot-broker-0.pinot-broker-headless.pinot-quickstart2.svc.cluster.local_8099,PATH=Root,Type=SPECTATOR has been registered. KeeperState: SyncConnected, instance: Broker_pinot-broker-0.pinot-broker-headless.pinot-quickstart2.svc.cluster.local_8099, type: SPECTATOR Handle new session, instance: Broker_pinot-broker-0.pinot-broker-headless.pinot-quickstart2.svc.cluster.local_8099, type: SPECTATOR Handling new session, session id: 1012fddef2b0003, instance: Broker_pinot-broker-0.pinot-broker-headless.pinot-quickstart2.svc.cluster.local_8099, instanceTye: SPECTATOR, cluster: pinot-quickstart fail to createClient. org.apache.helix.HelixException: Cluster structure is not set up for cluster: pinot-quickstart at org.apache.helix.manager.zk.ZKHelixManager.handleNewSession(ZKHelixManager.java:1124) ~[pinot-all-0.8.0-SNAPSHOT-jar-with-dependencies.jar:0.8.0-SNAPSHOT-47a75e5093129cc280de4c118434ccb337cd3da1]```
@fritzbx: I found the issue. I'm using AWS EKS, and the default storageClass is "gp2". The helm chart storageClass was set to "" and it didn't choose the default nor map to "gp2"
@xiangfu0: typically start order is: zookeeper/controller/(broker/servers/minion)
@xiangfu0: i thought the storageclass should be default?
@xiangfu0: which points to your system default one
@xiangfu0: e.g. ```➜ kt get storageclass NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE azurefile
@fritzbx: Looks like i have 2 defaults: ``` Warning FailedCreate 5m20s (x21 over 46m) statefulset-controller create Claim data-pinot-controller-0 for Pod pinot-controller-0 in StatefulSet pinot-controller failed error: persistentvolumeclaims "data-pinot-controller-0" is forbidden: Internal error occurred: 2 default StorageClasses were found Warning FailedCreate 5m20s (x21 over 46m) statefulset-controller create Pod pinot-controller-0 in StatefulSet pinot-controller failed error: failed to create PVC data-pinot-controller-0: persistentvolumeclaims "data-pinot-controller-0" is forbidden: Internal error occurred: 2 default StorageClasses were found```
@xiangfu0: oic
@xiangfu0: then this will fail
@xiangfu0: you nee to configure it explicitly
@fritzbx: Yes thanks. What would be a good storage for K8S deployment ?
@fritzbx: Would you recommend EBS ?
@xiangfu0: typically for controller you can use s3, server you can use ebs
@xiangfu0: for testing you can use ebs for both
@xiangfu0: controller should have access to deep store, which can be mounted ebs or s3
@fritzbx: Thanks. I'm planning to use S3 for deep storage as well
@xiangfu0: servers will talk to deep store through controller api(for mounted ebs cases) or s3 api
@xiangfu0: see:
@suresh.swaminathan69: @suresh.swaminathan69 has joined the channel
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
