Question: I am querying a table with index:

```
CREATE TABLE hwmd (cycle INT NOT NULL, id INT NOT NULL, ip INT NOT NULL, name CHAR(20) NOT NULL, uid INT NOT NULL, bin INT NOT NULL, num_data INT NOT NULL, task INT NOT NULL, utid INT NOT NULL, term_op INT NOT NULL, context INT NOT NULL);

CREATE INDEX idx_hwmd_id ON hwmd (id)

```

I make 2 queries on the same table with drastically varying speeds:

```
SELECT cycle, id FROM hwmd WHERE id = 100; // 38ms
SELECT cycle, id, ip FROM hwmd WHERE id = 100; // 1089ms

```

The second query that includes `ip` (INT field) takes 1089ms whereas the first query takes only 38ms. I confirmed both queries use the same index:

```
sqlite> explain query plan SELECT cycle, id FROM hwmd WHERE id = 100; 
QUERY PLAN
`--SEARCH hwmd USING INDEX idx_hwmd_id (id=?)

sqlite> explain query plan SELECT cycle, id, ip FROM hwmd WHERE id = 100; 
QUERY PLAN
`--SEARCH hwmd USING INDEX idx_hwmd_id (id=?)

```

Why would the second query take so long? How can I fix it?

Answer: 
```
volumes:
  taiga-static-data:
  taiga-media-data:
  taiga-db-data:
  taiga-async-rabbitmq-data:
  taiga-events-rabbitmq-data:

```

Base on your origin docker spec you can replace `persistentVolumeClaim` with `emptyDir`.

```
volumes:
- name: taiga-gateway-claim0
  emptyDir: {}
- name: taiga-static-data
  emptyDir: {}
- name: taiga-media-data
  emptyDir: {}

```

Or if you want to persist your data (continue using `persistentVolumeClaim`), you should create the PVC first:

```
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: taiga-gateway-claim0
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: taiga-static-data
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: taiga-media-data
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
  ...

```

The above spec will dynamically provision 3 persistent volumes for your pod using the default StorageClass on your **GKE** cluster.
The issue was that the persistent volumes are not bound to the pod hence the pod is failed to start. Ensure the storage is configured and the persistent volumes are created.