[JENKINS-57870] Request too large for server memory since 10.1.0

Type: Bug
Resolution: Fixed
Priority: Blocker
Component/s: p4-plugin
Labels:
- P4_VERIFY
Environment:
Jenkins ver. 2.164.3
p4-plugin : 1.10.0

Similar Issues:
Powered by SuggestiMate

Show

Hi,

When I use jenkins with swarm automated test,

I use the pipeline code like

checkout perforce(
   populate: previewOnly(quiet: true)
   workspace: templateSpec( ... )
)

and template workspace have all depot like

//depotA/... //$P4_CLIENT/depotA/...
//depotB/... //$P4_CLIENT/depotB/...
//depotC/... //$P4_CLIENT/depotC/...
...

and I create new workspace and delete after finished job always.

as you know, because I want to do like

unshelve files in the review item and run some test.

I don't need sync, sync -n or sync -k and flush, delete, whatever..

here's error message.

[Pipeline] container[Pipeline] {[Pipeline] checkout*
02:02:57* (p4):cmd:... p4 client -o TEMPLATE_SE_SWARM_AT_SA*
02:02:57* p4 client -o TEMPLATESE_SWARM_AT_SA*
02:02:57* 
02:02:57 (p4):stop:3*
02:02:57* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:57* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:57* 
02:02:58 (p4):stop:4*
02:02:58* (p4):cmd:... p4 client -i*
02:02:58* p4 client -i*
02:02:58* 
02:02:58 Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved.
02:02:58 
02:02:58 (p4):stop:5*
02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58* 
02:02:58 (p4):stop:6*
02:02:58* (p4):cmd:... p4 client -i*
02:02:58* p4 client -i*
02:02:58* 
02:02:58 Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved.
02:02:58 
02:02:58 (p4):stop:7*
02:02:58* (p4):cmd:... p4 client -f -s -t TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-s_
02:02:58 p4 client -f -s -t TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58* 
02:02:58 Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z switched.
02:02:58 
02:02:58 (p4):stop:8*
02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58* 
02:02:59 (p4):stop:9*
02:02:59* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:59* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:59* 
02:02:59 (p4):stop:10*
02:02:59* (p4):cmd:... p4 counter change*
02:02:59* p4 counter change*
02:02:59* 
02:02:59 (p4):stop:11*
02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/._
02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...
02:02:59 
02:02:59 Change 2688516 on 2019/06/05 by sj8282.park@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg'
02:02:59 (p4):stop:12*
02:02:59* (p4):cmd:... p4 counter change*
02:02:59* p4 counter change*
02:02:59* 
02:02:59 (p4):stop:13*
02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.__
02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516*
02:02:59* 
02:05:28 Operation 'user-changes' failed.
02:05:28 Request too large for server memory (try later?).
02:05:28 
02:05:28 (p4):stop:14

I need the option that create workspace without any changes, counter, ... other commands.

And by the way, this preview option is really needed?

who want to use p4 sync -nq , it's useless.

and p4 sync -n command also. I don't know when and why use this option.

is duplicated by

JENKINS-58116 "Request too large" in p4-plugin 1.10 (works with 1.9.7)

Closed

is related to

JENKINS-61745 Scan multibranch with date range or dop '@now'

Closed

Hokwang Lee created issue - 2019-06-06 00:52

Karl Wirth added a comment - 2019-06-06 09:38

Hi luckyhorang - This looks like a server error:

02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516
02:05:28 Operation 'user-changes' failed.02:05:28 Request too large for server memory (try later?).

I will therefore contact you directly to get more confidential information about the system and setup.

Karl Wirth added a comment - 2019-06-06 09:38 Hi luckyhorang - This looks like a server error: 02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516 02:05:28 Operation 'user-changes' failed.02:05:28 Request too large for server memory ( try later?). I will therefore contact you directly to get more confidential information about the system and setup.

Paul Allen added a comment - 2019-06-06 09:50

If you are using PreviewOnly with the quiet option set then the sync operation is skipped and you should see "P4 Task: skipping sync." in the log. (since version 1.9.5)

// Skip `p4 sync -q -n` to save compute time.
if (populate.isQuiet()) {
   log("P4 Task: skipping sync.");
   return;
}

Jenkins still needs to know what changes are associated with the build; this is for reporting, but also for polling calculations.

p4 changes -m1 -ssubmitted //CLIENT_SPEC/...@nnnn

Should not cause the server to report 'Request too large for server memory (try later?)'. Please work with our support team to get a copy of the Server log.

Paul Allen added a comment - 2019-06-06 09:50 If you are using PreviewOnly with the quiet option set then the sync operation is skipped and you should see "P4 Task: skipping sync." in the log. (since version 1.9.5) // Skip `p4 sync -q -n` to save compute time. if (populate.isQuiet()) { log( "P4 Task: skipping sync." ); return ; } Jenkins still needs to know what changes are associated with the build; this is for reporting, but also for polling calculations. p4 changes -m1 -ssubmitted //CLIENT_SPEC/...@nnnn Should not cause the server to report 'Request too large for server memory (try later?)'. Please work with our support team to get a copy of the Server log.

Karl Wirth made changes - 2019-06-06 09:53

Assignee

Original: Paul Allen [ p4paul ]

New: Karl Wirth [ p4karl ]

Karl Wirth made changes - 2019-06-06 09:53

Labels

New: P4_SUPPORT

Paul Allen added a comment - 2019-06-06 09:59

Please can you also include the client view mappings when reporting to support. (Exclusionary mappings could be very expensive.)

Paul Allen added a comment - 2019-06-06 09:59 Please can you also include the client view mappings when reporting to support. (Exclusionary mappings could be very expensive.)

Karl Wirth made changes - 2019-06-07 09:04

Description

Original: Hi,

When I use jenkins with swarm automated test,

I use the pipeline code like
{code:java}
checkout perforce(
populate: previewOnly(quiet: true)
workspace: templateSpec( ... )
)
{code}
and template workspace have all depot like
{code:java}
//depotA/... //$P4_CLIENT/depotA/...
//depotB/... //$P4_CLIENT/depotB/...
//depotC/... //$P4_CLIENT/depotC/...
...
{code}
and I create new workspace and delete after finished job always.

as you know, because I want to do like

unshelve files in the review item and run some test.

I don't need sync, sync -n or sync -k and flush, delete, whatever..

here's error message.
[Pipeline] container[Pipeline] {[Pipeline] checkout*02:02:57* (p4):cmd:... p4 client -o TEMPLATE__SE_SWARM_AT_SA*02:02:57* p4 client -o TEMPLATE__SE_SWARM_AT_SA*02:02:57* *02:02:57* (p4):stop:3*02:02:57* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:57* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:57* *02:02:58* (p4):stop:4*02:02:58* (p4):cmd:... p4 client -i*02:02:58* p4 client -i*02:02:58* *02:02:58* Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved.*02:02:58* *02:02:58* (p4):stop:5*02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* *02:02:58* (p4):stop:6*02:02:58* (p4):cmd:... p4 client -i*02:02:58* p4 client -i*02:02:58* *02:02:58* Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved.*02:02:58* *02:02:58* (p4):stop:7*02:02:58* (p4):cmd:... p4 client -f -s -t TEMPLATE__SE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-s___*02:02:58* p4 client -f -s -t TEMPLATE__SE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* *02:02:58* Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z switched.*02:02:58* *02:02:58* (p4):stop:8*02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* *02:02:59* (p4):stop:9*02:02:59* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:59* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:59* *02:02:59* (p4):stop:10*02:02:59* (p4):cmd:... p4 counter change*02:02:59* p4 counter change*02:02:59* *02:02:59* (p4):stop:11*02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.___*02:02:59* p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...*02:02:59* *02:02:59* Change 2688516 on 2019/06/05 by sj8282.park@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg'*02:02:59* (p4):stop:12*02:02:59* (p4):cmd:... p4 counter change*02:02:59* p4 counter change*02:02:59* *02:02:59* (p4):stop:13*02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.___*02:02:59* p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516*02:02:59* *02:05:28* Operation 'user-changes' failed.*02:05:28* Request too large for server memory (try later?).*02:05:28* *02:05:28* (p4):stop:14

I need the option that create workspace without any changes, counter, ... other commands.

And by the way, this preview option is really needed?

who want to use p4 sync -nq , it's useless.

and p4 sync -n command also. I don't know when and why use this option.

New: Hi,

When I use jenkins with swarm automated test,

I use the pipeline code like
{code:java}
checkout perforce(
populate: previewOnly(quiet: true)
workspace: templateSpec( ... )
)
{code}
and template workspace have all depot like
{code:java}
//depotA/... //$P4_CLIENT/depotA/...
//depotB/... //$P4_CLIENT/depotB/...
//depotC/... //$P4_CLIENT/depotC/...
...
{code}
and I create new workspace and delete after finished job always.

as you know, because I want to do like

unshelve files in the review item and run some test.

I don't need sync, sync -n or sync -k and flush, delete, whatever..

here's error message.
{code:java}
[Pipeline] container[Pipeline] {[Pipeline] checkout*
02:02:57* (p4):cmd:... p4 client -o TEMPLATE_SE_SWARM_AT_SA*
02:02:57* p4 client -o TEMPLATESE_SWARM_AT_SA*
02:02:57*
02:02:57 (p4):stop:3*
02:02:57* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:57* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:57*
02:02:58 (p4):stop:4*
02:02:58* (p4):cmd:... p4 client -i*
02:02:58* p4 client -i*
02:02:58*
02:02:58 Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved.
02:02:58
02:02:58 (p4):stop:5*
02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58*
02:02:58 (p4):stop:6*
02:02:58* (p4):cmd:... p4 client -i*
02:02:58* p4 client -i*
02:02:58*
02:02:58 Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved.
02:02:58
02:02:58 (p4):stop:7*
02:02:58* (p4):cmd:... p4 client -f -s -t TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-s_
02:02:58 p4 client -f -s -t TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58*
02:02:58 Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z switched.
02:02:58
02:02:58 (p4):stop:8*
02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:58*
02:02:59 (p4):stop:9*
02:02:59* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:59* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*
02:02:59*
02:02:59 (p4):stop:10*
02:02:59* (p4):cmd:... p4 counter change*
02:02:59* p4 counter change*
02:02:59*
02:02:59 (p4):stop:11*
02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/._
02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...
02:02:59
02:02:59 Change 2688516 on 2019/06/05 by sj8282.park@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg'
02:02:59 (p4):stop:12*
02:02:59* (p4):cmd:... p4 counter change*
02:02:59* p4 counter change*
02:02:59*
02:02:59 (p4):stop:13*
02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.__
02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516*
02:02:59*
02:05:28 Operation 'user-changes' failed.
02:05:28 Request too large for server memory (try later?).
02:05:28
02:05:28 (p4):stop:14
{code}

I need the option that create workspace without any changes, counter, ... other commands.

And by the way, this preview option is really needed?

who want to use p4 sync -nq , it's useless.

and p4 sync -n command also. I don't know when and why use this option.

Karl Wirth made changes - 2019-06-20 15:57

Link

New: This issue is duplicated by ~~JENKINS-58116~~ [ ~~JENKINS-58116~~ ]

Karl Wirth made changes - 2019-06-20 15:58

Summary

Original: populate: previewOnly(quiet: true) fail

New: Request too large for server memory since 10.1.0

Mateusz Delikat added a comment - 2019-06-28 10:32 - edited

p4karl, p4paul: Why are we actually seeing

02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...02:02:59 
02:02:59 Change 2688516 on 2019/06/05 by sj8282.park@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg'

and then

02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.__02:02:59
p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516*

when we already know the change number from the first call?

On our end we don't have "Request too large" errors but the first command on our stream takes about 1 second to complete and the second often takes more than 10 minutes. Does the plugin really needs to re-verify that changelist? Won't it be always the same?

Mateusz Delikat added a comment - 2019-06-28 10:32 - edited p4karl , p4paul : Why are we actually seeing 02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...02:02:59 02:02:59 Change 2688516 on 2019/06/05 by sj8282.park@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg' and then 02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.__02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516* when we already know the change number from the first call? On our end we don't have "Request too large" errors but the first command on our stream takes about 1 second to complete and the second often takes more than 10 minutes. Does the plugin really needs to re-verify that changelist? Won't it be always the same?

Assignee:: Unassigned

Reporter:: Hokwang Lee

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2019-06-06 00:52

Updated:: 2020-03-30 15:55

Resolved:: 2019-07-17 16:20

Jenkins

Details

Description

Attachments

Issue Links

Activity

Collapse comment: Karl Wirth added a comment - 2019-06-06 09:38

Expand comment: Karl Wirth added a comment - 2019-06-06 09:38

Collapse comment: Paul Allen added a comment - 2019-06-06 09:50

Expand comment: Paul Allen added a comment - 2019-06-06 09:50

Collapse comment: Paul Allen added a comment - 2019-06-06 09:59

Expand comment: Paul Allen added a comment - 2019-06-06 09:59

Collapse comment: Mateusz Delikat added a comment - 2019-06-28 10:32, Edited by Mateusz Delikat - 2019-06-28 10:33

Expand comment: Mateusz Delikat added a comment - 2019-06-28 10:32, Edited by Mateusz Delikat - 2019-06-28 10:33

People

Dates