# Point In Time creation failure after upgrade

**URL:** <https://discuss.elastic.co/t/point-in-time-creation-failure-after-upgrade/295172>\
**Category:** Elasticsearch\
**Tags:** point-in-time\
**Created:** [January 24, 2022, 1:59am UTC](https://discuss.elastic.co/t/point-in-time-creation-failure-after-upgrade/295172 "2022-01-24T01:59:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![RapTvin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raptvin/32/86995_2.png) [@RapTvin](https://discuss.elastic.co/u/RapTvin)\
**Post date:** [January 24, 2022, 1:59am UTC](https://discuss.elastic.co/t/point-in-time-creation-failure-after-upgrade/295172/1 "2022-01-24T01:59:23Z")

</div>

Hello, I need some help in an issue, I recently upgraded my Elasticsearch on local setup ( i.e downloaded 7.16.2 ). Now when I try to run a Point in Time API to retrieve the PIT id, on the Elasticsearch logs it gives me NPE saying that Point In Time is cannot be null, but as this is PIT creation call how can a PIT id be passed

```bash
> curl -X POST "localhost:9200/dummy_index/_pit?keep_alive=1m&pretty"

{
  "error" : {
    "root_cause" : [
      {
        "type" : "null_pointer_exception",
        "reason" : "Point in time parameter must be not null"
      }
    ],
    "type" : "null_pointer_exception",
    "reason" : "Point in time parameter must be not null"
  },
  "status" : 500
}

```

**Truncated Logs:**

```bash
path: /dummy_index/_pit, params: {pretty=, index=dummy_index, keep_alive=1m}
java.lang.NullPointerException: Point in time parameter must be not null
	at java.util.Objects.requireNonNull(Objects.java:246) ~[?:?]
	at org.elasticsearch.action.search.OpenPointInTimeResponse.<init>(OpenPointInTimeResponse.java:38) ~[elasticsearch-7.16.2.jar:7.16.2]
	at org.elasticsearch.action.search.TransportOpenPointInTimeAction.lambda$doExecute$1(TransportOpenPointInTimeAction.java:112) ~[elasticsearch-7.16.2.jar:7.16.2]
	at org.elasticsearch.action.ActionListener$MappedActionListener.onResponse(ActionListener.java:95) [elasticsearch-7.16.2.jar:7.16.2]
	at org.elasticsearch.action.ActionListener$RunAfterActionListener.onResponse(ActionListener.java:341) [elasticsearch-7.16.2.jar:7.16.2]
	at org.elasticsearch.action.search.AbstractSearchAsyncAction.start(AbstractSearchAsyncAction.java:196) [elasticsearch-7.16.2.jar:7.16.2]
	at org.elasticsearch.action.search.TransportSearchAction.executeSearch(TransportSearchAction.java:1045) [elasticsearch-7.16.2.jar:7.16.2]
	at org.elasticsearch.action.search.TransportSearchAction.executeLocalSearch(TransportSearchAction.java:761) [elasticsearch-7.16.2.jar:7.16.2]

```

---

<div class="post-metadata">

**Author:** ![RapTvin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raptvin/32/86995_2.png) [@RapTvin](https://discuss.elastic.co/u/RapTvin)\
**Post date:** [January 24, 2022, 10:05am UTC](https://discuss.elastic.co/t/point-in-time-creation-failure-after-upgrade/295172/2 "2022-01-24T10:05:12Z")

</div>

Bump

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 25, 2022, 12:50pm UTC](https://discuss.elastic.co/t/point-in-time-creation-failure-after-upgrade/295172/3 "2022-01-25T12:50:38Z")

</div>

Hey,

just tried the same locally on 7.16.2 and it worked. I created an index with a single document. Can you provide a full reproduction including index creation/mapping and the output of `curl localhost:9200/` ? Is that a single node cluster? Any cross cluster search involved? Thanks a lot!

--Alex

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 22, 2022, 12:51pm UTC](https://discuss.elastic.co/t/point-in-time-creation-failure-after-upgrade/295172/4 "2022-02-22T12:51:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.