Appreciate the response, Adam! We'll give that a shot and report back if we see any issues.
Thanks, Maggie -----Original Message----- From: Adam Kocoloski [mailto:kocol...@apache.org] Sent: Wednesday, October 24, 2018 1:25 PM To: user@couchdb.apache.org Subject: Re: View Issues Upgrading From 2.0.0 to 2.2.0 Hi Maggie, The mailing list strips out attached images, so that part didn’t come through. However, I think the stack trace is sufficient to figure this out. I suspect the `node2@dev02` node is still running 2.0.0, while elsewhere in the cluster an _all_docs HTTP request landed on a node in the cluster already running 2.2.0. It turns out that the RPC message format for this type of request changed in between 2.0 and 2.2, and as a result the 2.2 node is sending a message that the 2.0 node cannot understand. The 2.2 codebase contains an upgrade clause to understand the old message format; unfortunately the 2.0 node does not understand the new format and so the process for this request crashes. Upgrading the entire cluster to 2.2 ought to make this message disappear. We should do a better job of documenting these occasional RPC format changes and known good upgrade paths through them. Adam > On Oct 23, 2018, at 5:30 PM, maggie.ji...@tdameritrade.com.INVALID wrote: > > Hello, > > We are in the process of upgrading from 2.0.0 to 2.2.0. We are pretty close > but are seeing the below issues when verifying the installation. This is what > I see in the log files: > > [error] 2018-10-23T21:08:10.960427Z > dev-appinv2@devctlvsse00202.pteassociatesys.local > <mailto:dev-appinv2@devctlvsse00202.pteassociatesys.local> emulator -------- > Error in process <0.14288.0> on node 'node2@dev02' with exit value: > {{badmatch,{error,{function_clause,nil,[{fabric_rpc,all_docs,[<<"shards/40000000-5fffffff/ > > inventory.1539111041">>,[{user_ctx,{user_ctx,null,[<<"_admin">>],undefined}}],{mrargs,undefined,undefined,undefined,undefined,undefined,undefined,undefined,undefined,fwd,268435456,0,0,undefined,false,true,false,true,true,[],false,undefined,undefined,true,[{namespace,<<"_design">>}]}],[{file,"src/fabric_rpc.erl"},{line,95}]},{rexi_server,init_p,3,[{file,"src/rexi_server.erl"},{line,139}]}]}}},[{ddoc_cache_entry_validation_funs,recover,1,[{file,"src/ddoc_cache_entry_validation_funs.erl"},{line,33}]},{ddoc_cache_entry,do_open,1,[{file,"src/ddoc_cache_entry.erl"},{line,294}]}]} > > We think it might be related to the “inventory” database but that one has > never had views created. We’re not sure why it would be erroring out there? > > This is what the UI shows us: > > > Thank you, > > Maggie
