# Message not fully read (request) for \[\] and action \[\] log messages since upgrade to 19.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [March 6, 2012, 6:01am UTC](https://discuss.elastic.co/t/message-not-fully-read-request-for-and-action-log-messages-since-upgrade-to-19-0/6903 "2012-03-06T06:01:40Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Owen\_Butler\_2](https://avatars.discourse-cdn.com/v4/letter/o/b19c9b/32.png) [@Owen\_Butler\_2](https://discuss.elastic.co/u/Owen_Butler_2)\ **Post date:** [March 6, 2012, 6:01am UTC](https://discuss.elastic.co/t/message-not-fully-read-request-for-and-action-log-messages-since-upgrade-to-19-0/6903/1 "2012-03-06T06:01:40Z")
On a few instances, I'm seeing repeated log messages in the form: [2012-03-06 16:57:40,079][WARN][transport.netty] [index2.qa.acx] Message not fully read (request) for [38951] and action [], resetting [2012-03-06 16:57:42,431][WARN][transport.netty] [index2.qa.acx] Message not fully read (request) for [147443] and action [], resetting [2012-03-06 16:57:42,748][WARN][transport.netty] [index2.qa.acx] Message not fully read (request) for [146541] and action [], resetting [2012-03-06 16:57:44,980][WARN][transport.netty] [index2.qa.acx] Message not fully read (request) for [36339] and action [], resetting [2012-03-06 16:57:45,080][WARN][transport.netty] [index2.qa.acx] Message not fully read (request) for [38953] and action [], resetting [2012-03-06 16:57:47,434][WARN][transport.netty] [index2.qa.acx] Message not fully read (request) for [147445] and action [], resetting [2012-03-06 16:57:47,772][WARN][transport.netty] [index2.qa.acx] Message not fully read (request) for [146543] and action [], resetting [2012-03-06 16:57:50,013][WARN][transport.netty] [index2.qa.acx] Message not fully read (request) for [36341] and action [], resetting Each node in the cluster logs similar (but not exactly the same number) messages. I don't see this in instances that have been "nuked" while upgrading, IE, testing instances where the data directory has been cleared while upgrading. Only on instances that have seen an upgrade from 18.7. O ---
**Author:** ![Owen\_Butler\_2](https://avatars.discourse-cdn.com/v4/letter/o/b19c9b/32.png) [@Owen\_Butler\_2](https://discuss.elastic.co/u/Owen_Butler_2)\ **Post date:** [March 6, 2012, 6:26am UTC](https://discuss.elastic.co/t/message-not-fully-read-request-for-and-action-log-messages-since-upgrade-to-19-0/6903/2 "2012-03-06T06:26:41Z")
> I don't see this in instances that have been "nuked" while upgrading, > IE, testing instances where the data directory has been cleared while > upgrading. Only on instances that have seen an upgrade from 18.7. Actually, cancel that. I now see it in an instance where the data directory had been emptied during the downtime. Must be some other factor. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [March 6, 2012, 6:32am UTC](https://discuss.elastic.co/t/message-not-fully-read-request-for-and-action-log-messages-since-upgrade-to-19-0/6903/3 "2012-03-06T06:32:01Z")
Do you have clients / nodes that run 0.18 somewhere? On Tuesday, March 6, 2012 at 8:01 AM, Owen Butler wrote: > On a few instances, I'm seeing repeated log messages in the form: > > [2012-03-06 16:57:40,079][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [38951] and > action , resetting > [2012-03-06 16:57:42,431][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [147443] and > action , resetting > [2012-03-06 16:57:42,748][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [146541] and > action , resetting > [2012-03-06 16:57:44,980][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [36339] and > action , resetting > [2012-03-06 16:57:45,080][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [38953] and > action , resetting > [2012-03-06 16:57:47,434][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [147445] and > action , resetting > [2012-03-06 16:57:47,772][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [146543] and > action , resetting > [2012-03-06 16:57:50,013][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [36341] and > action , resetting > > Each node in the cluster logs similar (but not exactly the same > number) messages. > > I don't see this in instances that have been "nuked" while upgrading, > IE, testing instances where the data directory has been cleared while > upgrading. Only on instances that have seen an upgrade from 18.7. > > O ---
**Author:** ![Owen\_Butler\_2](https://avatars.discourse-cdn.com/v4/letter/o/b19c9b/32.png) [@Owen\_Butler\_2](https://discuss.elastic.co/u/Owen_Butler_2)\ **Post date:** [March 6, 2012, 6:55am UTC](https://discuss.elastic.co/t/message-not-fully-read-request-for-and-action-log-messages-since-upgrade-to-19-0/6903/4 "2012-03-06T06:55:03Z")
Almost certainly other nodes on the network running 18, or even 17.9. Equally, they would be configured with unique cluster names so wouldn't be trying to join the cluster, but perhaps pinging about to autodiscover? Now that you mention it, the rate of messages on the first instance I saw this on has slowed over time (perhaps as I go through and upgrade the other small clusters on the same network). Additionally, the cluster where I _did not_ see this, definitely doesn't have any other older nodes on the network (on it's own network). On Tuesday, March 6, 2012 5:32:01 PM UTC+11, kimchy wrote: > Do you have clients / nodes that run 0.18 somewhere? > > On Tuesday, March 6, 2012 at 8:01 AM, Owen Butler wrote: > > On a few instances, I'm seeing repeated log messages in the form: > > [2012-03-06 16:57:40,079][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [38951] and > action , resetting > [2012-03-06 16:57:42,431][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [147443] and > action , resetting > [2012-03-06 16:57:42,748][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [146541] and > action , resetting > [2012-03-06 16:57:44,980][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [36339] and > action , resetting > [2012-03-06 16:57:45,080][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [38953] and > action , resetting > [2012-03-06 16:57:47,434][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [147445] and > action , resetting > [2012-03-06 16:57:47,772][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [146543] and > action , resetting > [2012-03-06 16:57:50,013][WARN][transport.netty] > [index2.qa.acx] Message not fully read (request) for [36341] and > action , resetting > > Each node in the cluster logs similar (but not exactly the same > number) messages. > > I don't see this in instances that have been "nuked" while upgrading, > IE, testing instances where the data directory has been cleared while > upgrading. Only on instances that have seen an upgrade from 18.7. > > O ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [March 6, 2012, 7:30pm UTC](https://discuss.elastic.co/t/message-not-fully-read-request-for-and-action-log-messages-since-upgrade-to-19-0/6903/5 "2012-03-06T19:30:16Z")
Yes, the pinging method (if you use multicast) might cause this. On Tuesday, March 6, 2012 at 8:55 AM, Owen Butler wrote: > Almost certainly other nodes on the network running 18, or even 17.9. Equally, they would be configured with unique cluster names so wouldn't be trying to join the cluster, but perhaps pinging about to autodiscover? > > Now that you mention it, the rate of messages on the first instance I saw this on has slowed over time (perhaps as I go through and upgrade the other small clusters on the same network). > > Additionally, the cluster where I _did not_ see this, definitely doesn't have any other older nodes on the network (on it's own network). > > On Tuesday, March 6, 2012 5:32:01 PM UTC+11, kimchy wrote: > > > Do you have clients / nodes that run 0.18 somewhere? > > > > On Tuesday, March 6, 2012 at 8:01 AM, Owen Butler wrote: > > > > > On a few instances, I'm seeing repeated log messages in the form: > > > > > > [2012-03-06 16:57:40,079][WARN][transport.netty] > > > [index2.qa.acx] Message not fully read (request) for [38951] and > > > action , resetting > > > [2012-03-06 16:57:42,431][WARN][transport.netty] > > > [index2.qa.acx] Message not fully read (request) for [147443] and > > > action , resetting > > > [2012-03-06 16:57:42,748][WARN][transport.netty] > > > [index2.qa.acx] Message not fully read (request) for [146541] and > > > action , resetting > > > [2012-03-06 16:57:44,980][WARN][transport.netty] > > > [index2.qa.acx] Message not fully read (request) for [36339] and > > > action , resetting > > > [2012-03-06 16:57:45,080][WARN][transport.netty] > > > [index2.qa.acx] Message not fully read (request) for [38953] and > > > action , resetting > > > [2012-03-06 16:57:47,434][WARN][transport.netty] > > > [index2.qa.acx] Message not fully read (request) for [147445] and > > > action , resetting > > > [2012-03-06 16:57:47,772][WARN][transport.netty] > > > [index2.qa.acx] Message not fully read (request) for [146543] and > > > action , resetting > > > [2012-03-06 16:57:50,013][WARN][transport.netty] > > > [index2.qa.acx] Message not fully read (request) for [36341] and > > > action , resetting > > > > > > Each node in the cluster logs similar (but not exactly the same > > > number) messages. > > > > > > I don't see this in instances that have been "nuked" while upgrading, > > > IE, testing instances where the data directory has been cleared while > > > upgrading. Only on instances that have seen an upgrade from 18.7. > > > > > > O ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:37am UTC](https://discuss.elastic.co/t/message-not-fully-read-request-for-and-action-log-messages-since-upgrade-to-19-0/6903/6 "2017-07-06T03:37:08Z")