Getting Started

Expand all | Collapse all

webConsole configuration with node restart

  • 1.  webConsole configuration with node restart

    Posted 30 days ago
    Hello, I'm using gridgain webconsole with Apache Ignite.

    I started server node using 'ignite.sh  -v config-cache.xml &' command in linux server and add new cache named 'cache_add_test' at webconsole page.
    After restart the server also using ' ignite.sh  -v config-cache.xml &', there is no 'cache_add_test' cache.

    Is there any way if I add new cache at webconsole, update 'config-cache.xml' file? or is not possible?
    Should I seperate management configuration xml file with webconsole?

    Please help me...
    Thank you so much


    ------------------------------
    Grace Kim
    ------------------------------


  • 2.  RE: webConsole configuration with node restart

    Posted 30 days ago
    Hello!

    Cache configurations will survive restarts if your cluster has persistence configured.

    There is no obvious way to update XML config with caches created in Web Console, and such cache creation is expected to be mostly used during development/testing and not for production deployments. There's nothing wrong with such caches, it's just that your production process is expected to be repeatable without any user interaction.

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------



  • 3.  RE: webConsole configuration with node restart

    Posted 25 days ago
    Hello!
    Thank you so much for reply.
    Unfortunately, I think that should create cache&data region during production in my system operating environment.
    there are 8 nodes for production, have to add new cache&data region.
    Then, should I change configuration xml  and restart each node? and is it safe there are more node for rebalancing?

    Thank you

    ------------------------------
    Grace Kim
    programmer
    samsung
    ------------------------------



  • 4.  RE: webConsole configuration with node restart

    Posted 24 days ago
    Hello!

    You can add new cache by updating XML configuration on a single node before restarting it. To add new data region you would need to restart all nodes that should be affected. Please note that you cannot change configuration for an existing cache.

    Restarting a single node should be safe if you have sufficient backups configured for all caches.

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------



  • 5.  RE: webConsole configuration with node restart

    Posted 23 days ago
    Hello - I am trying to install web console on google kubernetes and facing issues. Just wanted to check if anyone has tried it before?

    Cheers,
    Lovell 
    --
    Sent from Gmail Mobile





  • 6.  RE: webConsole configuration with node restart

    Posted 23 days ago
    Hello!

    Have you tried going through the following documentation piece:
    Kubernetes Deployment
    Gridgain remove preview
    Kubernetes Deployment
    Web Agent is an application that connects a GridGain or Ignite cluster to the Web Console. For more information about Web Agent, please see the Getting Started Guide. When working with Web Agent in Kubernetes, you can either run Web Agent as a standalone application or in a container.
    View this on Gridgain >


    Then we can go through specific issues you encounter, if any.

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------



  • 7.  RE: webConsole configuration with node restart

    Posted 23 days ago
    Hi 

    Yes, i have tried following this document. I was successfully able to bring up the backend and the frontend servers. However when i try to register myself using the frontend link, it gives me a 404 error. Can you please advise what should i do next? 

    Cheers,
    Lovell






  • 8.  RE: webConsole configuration with node restart

    Posted 17 days ago
    Hello!

    We will need more context here (logs of K8S and Web Console).

    One thing to check: we have recently removed healthcheck probe and it needs to be disabled in K8S. Otherwise, health check fails, which may lead to Web Console not responding.
    Consider the following:
    https://www.gridgain.com/docs/web-console/latest/deploying-web-console-docker
    version: '2.4'
    services:
    backend:
    image: gridgain/gridgain-web-console-backend:2020.03.01
    # Restart on crash.
    restart: always
    environment:
    # Mail settings
    #- SPRING_MAIL_HOST=
    #- SPRING_MAIL_PORT=
    #- SPRING_MAIL_USERNAME=
    #- SPRING_MAIL_PASSWORD=
    - JVM_OPTS= volumes:
    - ${PWD}/work:/opt/gridgain-web-console-server/work frontend:
    image: gridgain/gridgain-web-console-frontend:2020.03.01
    ports:
    # Proxy HTTP nginx port (HOST_PORT:DOCKER_PORT)
    - 80:8008

    (healthcheck section should be absent)

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------



  • 9.  RE: webConsole configuration with node restart

    Posted 17 days ago
    Thanks for the inputs. I will check this and get back to you. 

    Meanwhile in the interim i have started using the public version of the web console and it works just fine. However i had a quick question, is there a way to provide custom names to my clusters in the web agent. With the auto generated names, it is quite difficult to identify various clusters. 

    Cheers,
    Lovell 






  • 10.  RE: webConsole configuration with node restart

    Posted 17 days ago
    I also had one more question - I am using the gridgain web agent container to connect to my ignite cluster. However i do not see a parameter to specify the db username and password in the yaml file. How do i use a db username and password. My ignite cluster has authentication on. 

    On Tue, May 19, 2020 at 2:50 PM Lovell Mathews <lovell.mathew@gmail.com> wrote:
    Thanks for the inputs. I will check this and get back to you. 

    Meanwhile in the interim i have started using the public version of the web console and it works just fine. However i had a quick question, is there a way to provide custom names to my clusters in the web agent. With the auto generated names, it is quite difficult to identify various clusters. 

    Cheers,
    Lovell 






  • 11.  RE: webConsole configuration with node restart

    Posted 16 days ago
    Hello!

    I believe you need to adjust default.properties file in the root of web-agent directory, by uncommenting and specifying:

    #Uncomment following options if needed:
    #node-uri=http://localhost:8080
    #node-login=ignite
    #node-password=ignite

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------



  • 12.  RE: webConsole configuration with node restart

    Posted 16 days ago
    Thanks Ilya, But since i am using a docker container I will have to have all these parameters in the YAML file. If i add these to default.properties i will have to keep making that change manually every time i bring up my container. 

    I have attached the list of the parameters in the YAML file currently. We do not have node-login and node-password as a part of the YAML file. 

    - name: NODE_URI
    # Replace "NODE_URI" value with service name for GridGain/Ignite cluster
    - name: SERVER_URI
    # Replace "SERVER_URI" value with Web Console service name
    - name: TOKENS
    # Replace "TOKENS" value with Security Token provided by Web Console
    value: 79036fc8-5c93-2118-8182-8ec01c845678






Would you attend a July Meetup?


Announcements