I working kibana dev platform

mr_searchng · September 25, 2019, 1:05pm

mr_searchng · September 25, 2019, 1:06pm

elastic/kibana/blob/master/CONTRIBUTING.md

# Contributing to Kibana

We understand that you may not have days at a time to work on Kibana. We ask that you read our contributing guidelines carefully so that you spend less time, overall, struggling to push your PR through our code review processes.

At the same time, reading the contributing guidelines will give you a better idea of how to post meaningful issues that will be more easily be parsed, considered, and resolved. A big win for everyone involved! :tada:

## Table of Contents

A high level overview of our contributing guidelines.

- [Effective issue reporting in Kibana](#effective-issue-reporting-in-kibana)
  - [Voicing the importance of an issue](#voicing-the-importance-of-an-issue)
  - ["My issue isn't getting enough attention"](#my-issue-isnt-getting-enough-attention)
  - ["I want to help!"](#i-want-to-help)
- [How We Use Git and GitHub](#how-we-use-git-and-github)
  - [Branching](#branching)
  - [Commits and Merging](#commits-and-merging)
  - [What Goes Into a Pull Request](#what-goes-into-a-pull-request)
- [Contributing Code](#contributing-code)
  - [Setting Up Your Development Environment](#setting-up-your-development-environment)

This file has been truncated. show original

I think heap size problem.

How can I solve ?

mr_searchng · September 25, 2019, 1:07pm

which shell config ?

flash1293 · September 25, 2019, 1:09pm

Hi @mr_searchng,

can you post the log output of your server here? It should contain hints on what exactly is going wrong

mr_searchng · September 25, 2019, 1:13pm

task manager screenshot

this problem heap size ,how can I solve ?

flash1293 · September 25, 2019, 1:16pm

The problem is most likely not the heap size, otherwise the server would crash completely. You have to set the environment variable "NODE_OPTIONS" in the environment from where you are starting your dev server (running yarn start)

mr_searchng · September 25, 2019, 1:18pm

mr_searchng · September 25, 2019, 1:19pm

joshdover · September 25, 2019, 3:38pm

You may be experiencing a heap OOM error, but it's not immediately clear. You should be able to customize the NODE_OPTIONS like this:

NODE_OPTIONS="--max_old_space_size=2048" node script/kibana.js --dev

From your logs, it also appears that Elasticsearch may not be running yet (or the logs you provided are not complete, I'm not sure). Did you start elasticsearch in another shell with yarn es snapshot?

mr_searchng · September 25, 2019, 5:52pm

NODE_OPTIONS="--max_old_space_size=2048"

we do this in which folder ?

mr_searchng · September 26, 2019, 8:08am

I wait answer,

Thanks

joshdover · September 26, 2019, 1:56pm

You should be able to run that all on the same command from the kibana repository that you cloned. @tylersmalley Is there anything different needed for setting this option on Windows?

tylersmalley · September 26, 2019, 5:44pm

It's not apparent to me that you are experiencing an out of memory error, do you have any logs which show this to be the issue?

In the original screenshot, it said there was a 500 error being returned. If you we're getting an OOM, the server would be crashed as Josh mentioned and would not return a 500. What branch are you running from, and do you have any plugins installed. To really help here, we need to see the server logs at the time you are seeing these 500 errors.

system · October 24, 2019, 5:44pm

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

Topic		Replies	Views
Javascript heap out of memeory Kibana	2	545	October 17, 2019
Image Panel in Kibana Kibana visualisation	0	12	July 18, 2024
Check Kibana max-old-space-size Kibana	10	5109	October 13, 2020
Kibana dreaded timeout on dashboard Kibana	24	18467	April 19, 2017
Out-of-memory issues in 7.6 Kibana	3	2445	June 1, 2020

I working kibana dev platform

Related Topics