title: How does the distributed executor service in Redisson work with regards to scoping / closuring?
body: <p>If I push a Runnable to a <strong>redisson</strong> distributed executor service, what rules am I required to oblige by?</p>
  <p><strong>Surely</strong> , I can not have free reign, I do not see how that is possible, yet, it is not mention in the docs at all, nor are any rules apparently enforced by the API, like R extends Serializable or similar.</p>
  <p>If I pass this runnable:</p>
  <pre><code>new Runnable(()-&gt; {
      // What can I access here, and have it be recreated in whatever server instance picks it up later for execution? 
  
  
      // newlyCreatedInstanceCreatedJustBeforeThisRunnableWasCreated.isAccissible(); // ?
  
      // newlyComplexInstanceSuchAsADatabaseDriverThatisAccessedHere.isAccissible(); // ?
  
      // transactionalHibernateEntityContainingStaticReferencesToComplexObjects....
     
      // I think you get the point. 
  
      // Does Redisson serialize everything within this scope? 
  
      // When it is recreated later, surely, I can not have access to those exact objects, unless they run on the same server, right? 
  
      // If the server goes does and up, or another server executes this runnable, then what happens? 
  
      // What rules do we have to abide by here?
  
  })
  </code></pre>
  <p>Also, what rules do we have to abide by when pushing something to a RQueue, RBlockingDequeu, or Redisson live objects?</p>
  <p>It is not clear from the docs.</p>
  <p>Also, would be great if a link to a single site documentation site could be provided. The one here requires a lot of clickin and navigation:</p>
  <p><a href="https://github.com/redisson/redisson/wiki/Table-of-Content" rel="nofollow noreferrer">https://github.com/redisson/redisson/wiki/Table-of-Content</a></p>