RE: How to test if slrp is working correctly

No one able to help? ;) -Original Message- To: user Subject: How to test if slrp is working correctly I am testing with slrp and csi drivers after watching this video[1] of mesosphere. I would like to know how I can verify that the slrp is properly configured and working. 1. Can

How to test if slrp is working correctly

?00:01:00 ./test-csi-plugin --available_capacity=2GB --work_dir=workdir 16292 16283 0 Aug15 ?00:00:05 ./csilvm -unix-addr=unix:///run/csilvm.sock -volume-group VGtest 17639 17636 0 Aug15 ?00:00:08 ./csinfs --endpoint unix://run/csinfs.sock --nodeid test

RE: mesos csi test plugin slrp 401 Unauthorized

If I disable authenticate_http_readwrite authenticate_http_readonly. My test slrp's are indeed loaded and I see tasks running. Launching these tasks as described on the manual page via curl[1] also fails. The task is not running, but I see that curl commands json is being put

test-csi-plugin should work?

/cni/test-csi-plugin': free(): invalid pointer: 0x7f5e1ea25a10 *** === Backtrace: = /lib64/libc.so.6(+0x81299)[0x7f5e18dcc299] /usr/libexec/cni/test-csi-plugin(_ZN9__gnu_cxx13new_allocatorIPNSt8__det ail15_Hash_node_baseEE10deallocateEPS3_m+0x20)[0x5631f93bc1b0] /usr/libexec/cni/test

mesos csi test plugin slrp 401 Unauthorized

I am testing with this Failed to recover resource provider with type 'org.apache.mesos.rp.local.storage' and name 'test_slrp': Failed to get containers: Unexpected response '401 Unauthorized' (401 Unauthorized.) Is this because I am having authentication on, and the standalone container

Re: [External Email] Re: Simulate Mesos for Large Scale Framework Test

plemented. At least, I am not > aware of such simulators. > > If you want to simulate with your own framework, one possibility is to run > multiple agents with fake resources on the same (or a few) node. > > Alternatively, we have a lightweight benchmark test suite inside Mesos f

Re: Simulate Mesos for Large Scale Framework Test

benchmark test suite inside Mesos for the allocator: https://github.com/apache/mesos/blob/master/src/tests/hierarchical_allocator_benchmarks.cpp#L128 You can easily specify agent and framework <https://github.com/apache/mesos/blob/dcd73437549413790751d1ff127989dbb29bd753/src/te

Simulate Mesos for Large Scale Framework Test

Dear all, I developed a framework and would like to test the scheduling algorithm by simulating it in a large scale environment. I found an old doc at https://docs.google.com/document/d/1Ygq9MPWrqcQLf0J-mraVeEIRYk3xNXXQ0xRHFqTiXsQ/edit# <https://docs.google.com/document/d/1Ygq9MPWrqcQL

Re: Docker image for fast e2e test with Mesos

ts, > so that running the entire stack will be just a single `docker run`. > Another goal I want to achieve is to test unreleased Mesos versions. > > - Jie > > On Sun, Feb 11, 2018 at 4:21 PM, Craig Wickesser <codecr...@gmail.com> > wrote: > > > Might be worth

Re: Docker image for fast e2e test with Mesos

goal I want to achieve is to test unreleased Mesos versions. - Jie On Sun, Feb 11, 2018 at 4:21 PM, Craig Wickesser <codecr...@gmail.com> wrote: > Might be worth checking out mini-mesos as well https://www.minimesos.org > > On Sun, Feb 11, 2018 at 7:05 PM Jie Yu <yujie@gmail.c

Re: Docker image for fast e2e test with Mesos

amework developers to quickly > test with Mesos APIs (preferably new APIs that haven't been released yet). > The docker container will have both Mesos master and agent running, > allowing framework developers to easily write e2e integration tests with > Mesos. > > Therefore, I went a

Docker image for fast e2e test with Mesos

Hi, When we were developing a framework with Mesos, we realized that it'll be great to have a Docker image that allows framework developers to quickly test with Mesos APIs (preferably new APIs that haven't been released yet). The docker container will have both Mesos master and agent running

Re: Test framework stalled

u image via >> http://imgur.com/ or any other website? >> >> On Tue, Jun 20, 2017 at 9:49 PM, Joao Costa <labremoted...@gmail.com> >> wrote: >> >> > Hi guys, >> > >> > Can anyone help me with this problem: >> > >> > Eve

Re: Test framework stalled

Seems the mailing list drop your image. May you share you image via http://imgur.com/ or any other website? On Tue, Jun 20, 2017 at 9:49 PM, Joao Costa <labremoted...@gmail.com> wrote: > Hi guys, > > Can anyone help me with this problem: > > Every time I try to run the te

Re: Proposal for evaluating Mesos scalability and robustness through stress test.

ty limit/bottleneck to Mesos' >> > centralized architecture and what is its robustness in the face of >> various >> > failures. If we can identify them in advance, probably we can manage and >> > optimize them before we are suffering in any potential performan

Re: Proposal for evaluating Mesos scalability and robustness through stress test.

suffering in any potential performance > degradations. > > To explore Mesos' capability and break the knowledge gap, we have a > proposal to evaluate Mesos scalability and robustness through stress test, > the draft of which can be found at: draft_link > <https://docs.google.com/documen

Proposal for evaluating Mesos scalability and robustness through stress test.

. To explore Mesos' capability and break the knowledge gap, we have a proposal to evaluate Mesos scalability and robustness through stress test, the draft of which can be found at: draft_link <https://docs.google.com/document/d/10kRtX4II74jfUuHJnX2F5teqpXzHYFQAZGWjCdS3cZA/edit?usp=sharing>. Pleas

Re: test

Don't sweat about the test email. Not a big deal. Welcome to the community! On Wed, Jul 13, 2016 at 1:51 PM, Rahul Palamuttam <rahulpala...@gmail.com> wrote: > I'm truly sorry. > Just kept getting several message denied errors, until I realized I needed > to send a reply to user

Re: test

Why are you wasting our time with this? Lame. *...* *Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872* On Wed, Jul 13, 2016 at 11:56 AM, Rahul Palamuttam wrote: > >

test

Re: Help interpreting output from running java test-framework example

operations >>> and support but given the strong perforrmance and stability characterstics >>> we are initially seeing here that effort is likely to get underway. >>> >>> >>> >>> 2015-09-09 12:54 GMT-07:00 Vinod Kone <vinodk...@gmail.com>: >>>

Re: Help interpreting output from running java test-framework example

s we are initially seeing here that effort is likely to get >>>> underway. >>>> >>>> >>>> >>>> 2015-09-09 12:54 GMT-07:00 Vinod Kone <vinodk...@gmail.com>: >>>> >>>>> sounds like it. can you

Re: Help interpreting output from running java test-framework example

gt; >>> >>> I am in the process of learning how to run a mesos cluster with the >>> intent for it to be the resource manager for Spark. As a small step in >>> that direction a basic test of mesos was performed, as suggested by the >>> Mesos Getting Start

Re: Help interpreting output from running java test-framework example

y seeing here that effort is likely to get underway. >> >> >> >> 2015-09-09 12:54 GMT-07:00 Vinod Kone <vinodk...@gmail.com>: >> >>> sounds like it. can you see what the slave/agent and executor logs say? >>> >>> On Tue, Sep 8, 2015 at 11:

Re: Help interpreting output from running java test-framework example

gt;> >> I am in the process of learning how to run a mesos cluster with the >> intent for it to be the resource manager for Spark. As a small step in >> that direction a basic test of mesos was performed, as suggested by the >> Mesos Getting Started page. >> >> I

Re: Help interpreting output from running java test-framework example

As a small step in that > direction a basic test of mesos was performed, as suggested by the Mesos > Getting Started page. > > In the following output we see tasks launched and resources offered on a > 20 node cluster: > > [stack@yarnmaster-8245 build]$ ./src/examples/java/test-framew

Help interpreting output from running java test-framework example

I am in the process of learning how to run a mesos cluster with the intent for it to be the resource manager for Spark. As a small step in that direction a basic test of mesos was performed, as suggested by the Mesos Getting Started page. In the following output we see tasks launched

Re: make[3]: *** [check-local] Aborted (core dumped) in make test

This cases might show that LogZooKeeperTest and MasterAuthorizationTest affect each other. joma@kopernikus-u:~/dev/programme/mesos/build/mesos/build$ make check GTEST_FILTER=MasterAuthorizationTest.* Test Run OK. joma@kopernikus-u:~/dev/programme/mesos/build/mesos/build$ make check

Re: make[3]: *** [check-local] Aborted (core dumped) in make test

With latest, do you refer to the latest revision in trunk? Then no, I have tested against Release/Tag 0.22.1. Should i try with latest? On 2015-05-18 18:49, haosdent wrote: @Joerg Maurer I could not reproduce your problems in CentOS. From this

Re: make[3]: *** [check-local] Aborted (core dumped) in make test

information for your investigation? (1) joma@kopernikus-u:~/dev/programme/mesos/build/mesos/build$ make check GTEST_FILTER=MasterAuthorizationTest.SlaveRemoved GTEST_REPEAT=1000 GTEST_BREAK_ON_FAILURE=1 ... Repeating all tests (iteration 1000) . . . Note: Google Test filter

Re: make[3]: *** [check-local] Aborted (core dumped) in make test

/programme/mesos/build/mesos/build$ make check GTEST_FILTER=MasterAuthorizationTest.SlaveRemoved GTEST_REPEAT=1000 GTEST_BREAK_ON_FAILURE=1 ... Repeating all tests (iteration 1000) . . . Note: Google Test filter = MasterAuthorizationTest.SlaveRemoved

Re: make[3]: *** [check-local] Aborted (core dumped) in make test

1000) . . . Note: Google Test filter = MasterAuthorizationTest.SlaveRemoved

Re: make[3]: *** [check-local] Aborted (core dumped) in make test

That's an error from our JSON parsing library, picosjson. I'm surprised that our metrics JSON output is invalid according to picojson. Is this error repeatable? You can test with: make check GTEST_FILTER=MasterAuthorizationTest.SlaveRemoved GTEST_REPEAT=1000 GTEST_BREAK_ON_FAILURE=1 On Fri, May

Re: Can not finish ./src/test-framework

You can set LD_LIBRARY_PATH to include /root/mesos-0.19.1/build/src/.libs/ on your machine For example, `LD_LIBRARY_PATH=/root/mesos-0.19.1/build/src/.libs/ ./src/test-framework --master=192.168.122.5:5050` Or run make install and get the mesos library to a well known library location. If you

Re: Running test-executor

should be logged in the slave's log during the time of the launch. FWIW, the test-executor did run successfully, because the tasks wouldn't have reached TASK_FINISHED state (state 2) otherwise. On Thu, Jul 3, 2014 at 1:57 PM, Sammy Steele sammy_ste...@stanford.edu wrote: Hi Vinod, Thanks

Running test-executor

I am trying to figure out how to run the python test-executor given in the mesos code base. Based on the documentation at: http://mesos.apache.org/documentation/latest/app-framework-development-guide/, I tried starting my slaves with the command: ./bin/mesos-slave.sh --ip=10.79.6.72 --master

Re: Running test-executor

Sammy, You need to run a framework to be able to run an executor. See http://mesos.apache.org/gettingstarted/ to see how to run the example python framework. On Thu, Jul 3, 2014 at 11:29 AM, Sammy Steele sammy_ste...@stanford.edu wrote: I am trying to figure out how to run the python test

Re: Running test-executor

Hi Vinod, Thanks for your advice. That is what I originally thought, and I was originally trying to run the test-executor through the test-framework provided in the same examples folder. For some reason the test-executor doesn't appear to execute when I run the test-framework. The output