Hi Marton,
   Do you have a patch for RATIS-95, I don’t see one attached.

Thanks
jitendra

On 7/27/17, 5:36 AM, "Marton, Elek" <h...@anzix.net> wrote:

    Hi, thx the answer.
    
    I created multiple issues (RATIS-94/95).
    
    I uploaded a patch to RATIS-95.
    
    Two questions:
    
    1. Is there any status equivalent to Hadoop PATCH_AVAILABLE? What should 
    I do if the patch is read for review?
    
    2. I need to turn on clean-shade profile for 'mvn clean' to delete the 
    generated files. It was a little bit confising for me, as a simple clean 
    doesn't delete all the created files. Not a big deal, but is there any 
    reason why it's not run automaticaly during a maven clean? I if it just 
    beacuse some maven issues/limitation I would be happy to investigate it...
    
    Marton
    
    On 07/03/2017 08:19 PM, Jing Zhao wrote:
    > Elek, great proposals! I've added you to the contributor list. Please feel
    > free to create jiras and assign them to yourself.
    > 
    > On Sat, Jul 1, 2017 at 2:09 PM, Marton, Elek <h...@anzix.net> wrote:
    > 
    >>
    >> Hi,
    >>
    >> I would like to contribute to Ratis.
    >>
    >> I have two proposals:
    >>
    >>   1. I would like to create and register JMX beans for every 
RaftServerImpl
    >> to display at least the current leader, term, index,...
    >>
    >>     I would like to show this information from the (under devepolment)
    >> Ozone web ui interfaces.
    >>
    >>   2. I would like to add a simple Server and Client class to the example
    >> project. Currently it could be tested only from unit test. I think it 
would
    >> be more easily to try out ratis by starting standalon example servers 
with
    >> `java -jar...`. (And check on the JMX interface, if everything is 
fine...)
    >>
    >>
    >> Please comment my ideas, and if agree, add my user (
    >> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elek) to the
    >> contributors group.
    >>
    >> Thanks
    >> Marton
    >>
    > 
    
    

Reply via email to