lhotari opened a new pull request #13025:
URL: https://github.com/apache/pulsar/pull/13025


   ### Motivation
   
   The changes in #11285 broke `pulsar-perf` and it fails with error 
   ```
   root@3b36a0ea475b:/pulsar# ./bin/pulsar-perf produce 
   [0.000s][error][logging] Error opening log file 'logs/pulsar_gc_14.log': No 
such file or directory
   [0.000s][error][logging] Initialization of output 
'file=logs/pulsar_gc_%p.log' using options 'filecount=10,filesize=20M' failed.
   Invalid -Xlog option 
'-Xlog:gc*:logs/pulsar_gc_%p.log:time,uptime:filecount=10,filesize=20M', see 
error log for details.
   Error: Could not create the Java Virtual Machine.
   Error: A fatal exception has occurred. Program will exit.
   ```
   
   When analyzing the problem, it seems that the usage of 
`PULSAR_EXTRA_OPTS`/`BOOKIE_EXTRA_OPTS` environment variables isn't correctly 
used. It should be possible to use PULSAR_EXTRA_OPTS / BOOKIE_EXTRA_OPTS to add 
additional environment variables. This PR fixes that issue.
   
   ### Modifications
   - don't combine variables in `BOOKIE_EXTRA_OPTS`
   - don't add `PULSAR_GC_LOG` to `PULSAR_EXTRA_OPTS`
   - make `BOOKIE_GC_LOG` default to `PULSAR_GC_LOG` for consistency
   - apply `PULSAR_EXTRA_OPTS` and `BOOKIE_EXTRA_OPTS` after other settings so 
that it is possible to override
     settings defined by `PULSAR_MEM` / `PULSAR_GC` / `BOOKIE_MEM` / 
`BOOKIE_GC`.
   
   <!--
   ### Contribution Checklist
     
     - Name the pull request in the form "[Issue XYZ][component] Title of the 
pull request", where *XYZ* should be replaced by the actual issue number.
       Skip *Issue XYZ* if there is no associated github issue for this pull 
request.
       Skip *component* if you are unsure about which is the best component. 
E.g. `[docs] Fix typo in produce method`.
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
     
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
     
     - Each commit in the pull request has a meaningful commit message
   
     - Once all items of the checklist are addressed, remove the above text and 
this checklist, leaving only the filled out template below.
   
   **(The sections below can be removed for hotfixes of typos)**
   -->
   
   *(If this PR fixes a github issue, please add `Fixes #<xyz>`.)*
   
   Fixes #<xyz>
   
   *(or if this PR is one task of a github issue, please add `Master Issue: 
#<xyz>` to link to the master issue.)*
   
   Master Issue: #<xyz>
   
   ### Motivation
   
   
   *Explain here the context, and why you're making that change. What is the 
problem you're trying to solve.*
   
   ### Modifications
   
   *Describe the modifications you've done.*
   
   ### Verifying this change
   
   - [ ] Make sure that the change passes the CI checks.
   
   *(Please pick either of the following options)*
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   *(or)*
   
   This change is already covered by existing tests, such as *(please describe 
tests)*.
   
   *(or)*
   
   This change added tests and can be verified as follows:
   
   *(example:)*
     - *Added integration tests for end-to-end deployment with large payloads 
(10MB)*
     - *Extended integration test for recovery after broker failure*
   
   ### Does this pull request potentially affect one of the following parts:
   
   *If `yes` was chosen, please highlight the changes*
   
     - Dependencies (does it add or upgrade a dependency): (yes / no)
     - The public API: (yes / no)
     - The schema: (yes / no / don't know)
     - The default values of configurations: (yes / no)
     - The wire protocol: (yes / no)
     - The rest endpoints: (yes / no)
     - The admin cli options: (yes / no)
     - Anything that affects deployment: (yes / no / don't know)
   
   ### Documentation
   
   Check the box below and label this PR (if you have committer privilege).
   
   Need to update docs? 
   
   - [ ] `doc-required` 
     
     (If you need help on updating docs, create a doc issue)
     
   - [ ] `no-need-doc` 
     
     (Please explain why)
     
   - [ ] `doc` 
     
     (If this PR contains doc changes)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to